Use WAM-compatible authentication modules

[skirkpatrickMSFT]

🗣 Description

• Remove the use of embedded browser authentication.
• Require MicrosoftTeams 7.9.0 for WAM-compatible Teams authentication.
• Support Microsoft.Graph.Authentication versions 2.30 through 2.38.1 without pinning the dependency.
• Force the support module to reload current dependency metadata.
• Import Trace-ScubaFunction directly into the AAD provider so privileged-role and privileged-user collection can log correctly.
• Update the dependency documentation to match the supported versions.

💭 Motivation and context

The previous authentication module versions could invoke browser-based interactive authentication and retained stale dependency metadata in an existing PowerShell session. Updating the supported modules enables WAM authentication while preserving delegated and service-principal flows. The AAD provider import also ensures its logging helper is available in production module scope.

Closes #2305.

🧪 Testing

• Local focused Pester tests: 30 passed, 0 failed.
• Functional tests passed.
• Smoke tests passed.
• Manually validated delegated AAD and Teams authentication against a GCC tenant using WAM.

✅ 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 automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

• PR passed smoke test check.

• PR/feature branch passes functional tests for relevant products, if applicable.

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

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

• Resolved all merge conflicts on branch.

• Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Close issues resolved by this PR if the closing keywords did not activate.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.