Update Teams testplans that test policy 4.1 (test plan variants e# and gcc)

[nanda-katikaneni]

🗣 Description

This PR updates Teams test plan variants that test policy 4.1. Recent changes to the Set-CsTeamsClientConfiguration require an additional input parameter. The two appropriate test plans have been updated to add an additional pre-condtion to pass the 'identity' parameter.

💭 Motivation and context

Closes #1545

🧪 Testing

• Run the Teams functional test plan for the variant e# using a E5/E3 tenant
• Ensure that test plans run without errors and correctly pass/fail the tests

📷 Screenshots (if appropriate)

Ran the e# and gcc variant teams test plans on appropriate tenants and both compliant and non-complaint test cases passed.

✅ 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.

[schrolla]

Ran Teams functional tests using updated test plan against all four test tenants using either the e# or gcc plan as approrpriate for the given tenant. All worked and passed. Also reverted MicrosoftTeams library to oldest allowable by SG (4.9.3) and the test plan still worked properly so the new parameter has been present for some time and only change was it became mandatory. So no breakage when backtesting.
Good update, looks good to go to me.

[ahuynhMITRE]

no issues to report with running the functional test plan for Teams. No other comments from me!