[CI Environment] Token Mechanism Uplift (support tokens as GitHub Secret + Migrate Settings.Json to Settings YAML)

[ahmadabdalla]

Closes #1440

Description

• Migrated from global.variables.yml and settings.json into a single settings.yml
• Support for a GitHub secret / ADO variable named TOKEN_NAMEPREFIX which takes precedence over the localToken_namePrefix that exists in the settings.yml
• Updated documentation

Details

• Pester tests changed to now receive an input of the token as a configuration instead of the pester test file having to process the settings and extract content from it.
• unified the experience for token replacement across multiple scripts and pipelines
• GitHub Module Workflows contain a new Environment Variable called TOKEN_NAMEPREFIX, this is not used if the secret is not specified
• Updated documentation especially referencing the need for the powershell-yaml module in the scenario 2 - contribution documentation.

Experience for new TOKEN

If not defined as a secret in GHA / variable in ADO:

If defined as a secret in GHA/ADO variable:

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change

Please delete options that are not relevant.

• Bugfix (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 not work as expected)
• Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code

[github-actions]

Unit Test Results

46 tests   45 ✔️  18s ⏱️
  1 suites    1 💤
  1 files      0 ❌

Results for commit f98b02b.