Correcting the habitat pipeline issue for Windows

[johnmccrae]

Signed-off-by: John john.mccrae@progress.com

Description

The habitat-test.yml file was calling PowerShell command directly. This is hugely problematic since things like the $env variable weren't respected and that resulted in errors; for example calling $env:path would result in an error similar to :path is not recognized notice that the $env variable was chopped. In total this resulted in improper and incomplete execution. This update fixes that by moving the offending code to a distinct .ps1 file and calling on that; which does work.

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.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[johnmccrae]

Failing tests are known and being resolved elsewhere