Move habitat-test to public

[tpowell-progress]

Description

Allows habitat test results to actually visible to community members making PRs

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[muthuja]

At the moment, there’s some ongoing internal discussion around this change, specifically related to the use of an internal gem and how it should be handled in public builds. We want to make sure we approach this in a way that’s consistent and sustainable for the project as a whole.

Because of this, we’re pausing progress on this PR until we have more clarity and alignment internally. We’ll be sure to update this thread as soon as we have more information or next steps. Thanks again for your understanding

cc @jaymzh @tpowell-progress @Vasu1105 @clintoncwolfe @rahulgoel1 @ashiqueps @neha-p6