feat: allow deep folders in stack config path

[toddgiguere]

Description

Changed logic in testprojects package to allow TestProjectsOptions.StackConfigurationPath and other path properties to support nested folders inside of the project (previously only supported config files in root of project).

Release required?

• [ ] No release
• [ ] Patch release (x.x.X)
• [x] Minor release (x.X.x)
• [ ] Major release (X.x.x)

Release notes content

TestProjectsOptions.StackConfigurationPath, and the other path variables in same structure, now support nested folder structure within the repository to locate configuration files.

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• [ ] If relevant, a test for the change is included or updated with this PR.
• [ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[toddgiguere]

/run pipeline

[terraform-ibm-modules-ops]

:tada: This issue has been resolved in version 1.37.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: