Updated Microsoft.PowerApps.Administration.PowerShell min/max versions

[schrolla]

🗣 Description

Updated RequiredVersions.ps1 file to update the Microsoft.PowerApps.Administration.PowerShell minimum and maximum versions to support pinning to versions newer than the bugged 2.0.197 version.

• Min version set to 2.0.198
• Max version re-pinned to 2.0.203

💭 Motivation and context

Allows users to use newer working versions of the PowerApps admin module while preventing installation of the 2.0.197 bugged version.

Closes #1409

🧪 Testing

• Remove existing ScubaGear dependencies from your test machine. Either by running Uninstall-Module for each dependency OR go to your Documents/WindowsPowerShell/Modules folder and delete all ScubaGear dependent modules.
• Import the ScubaGear module from the feature branch (Import-Module PowerShell/ScubaGear).
• Run Initialize-ScubaGear
• Validate that the version of Microsoft.PowerApps.Administration.PowerShell installed is > 2.0.197
• Run Invoke-SCuBA -p powerplatform and confirm it works as intended

📷 Screenshots (if appropriate)

Example of running Initialize-SCuBA with the updated dependencies in RequiredVersions.ps1

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• PR targets the correct parent branch (e.g., main or release-name) for merge.
• Changes are limited to a single goal - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• All future TODOs are captured in issues, which are referenced in code comments.
• These code changes follow the ScubaGear content style guide.
• Related issues these changes resolve are linked preferably via closing keywords.
• All relevant type-of-change labels added.
• All relevant project fields are set.
• All relevant repo and/or project documentation updated to reflect these changes.
• Unit tests added/updated to cover PowerShell and Rego changes.
• Functional tests added/updated to cover PowerShell and Rego changes.
• All relevant functional tests passed.
• All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

• PR passed smoke test check.

• Feature branch has been rebased against changes from parent branch, as needed

  Use Rebase branch button below or use this reference to rebase from the command line.

• Resolved all merge conflicts on branch

• Notified merge coordinator that PR is ready for merge via comment mention

• Demonstrate changes to the team for questions and comments.
  (Note: Only required for issues of size Medium or larger)

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

[twneale]

Seems pretty straightforward 🤔👍

[buidav]

No issues with v2.0.198 nor v2.0.203 on my end.
Didn't check the in between versions but a little googling show no issues with the other versions. ScubaGear will max install v2.0.203 by default as well anyway.
LGTM.

[schrolla]

@nanda-katikaneni This PR is ready for merge.