Functional testing workflow - update Teams test plan and it variant's

[nanda-katikaneni]

💡 Summary

The current Nightly Functional Testing workflow has following combination of tests for Teams:

• E5 tenant: teams.testplan.yaml and teams.e#.testplan.yaml
• G5,G3 and GCCHIGH tenants (all three tenants): teams.testplan.yaml and teams.gcc.testplan.yaml

In the above, the gcc test plan variant is not needed to run (the specific test in the plan does not apply to gcc tenants - test plan is more a place holder for any future gcc specific tests - none yet). Proposing the following combination runs:

Nightly Functional Testing (Mon-Fri):

• E5 tenant: teams.testplan.yaml and teams.e#.testplan.yaml
• G3/G5 tenants: teams.testplan.yaml

Motivation and context

The gcc test plan variant is a placeholder for any future gcc specific tests - the current test in that plan is not needed (it is a test designed for non-gcc tenants).

Acceptance criteria

Nightly functional tests for teams run only with valid test plans.

[james-garriss]

While written for Teams, it's possible that the solutions that Nanda proposes are applicable to other products as well.

[nanda-katikaneni]

Updated this issue for updating the current workflow with appropriate Teams test plans. The change of schedule will be taken up separately (possibly along with other products).