move M365 creds rotation logic to code

[HiteshRepo]

moves M365 creds rotation logic to code

Does this PR need a docs update or release note?

• ✅ Yes, it's included
• 🕐 Yes, but in a later PR
• ⛔ No

Type of change

• 🌻 Feature
• 🐛 Bugfix
• 🗺️ Documentation
• 🤖 Supportability/Tests
• 💻 CI/Deployment
• 🧹 Tech Debt/Cleanup

Issue(s)

#5080

Test Plan

• 💪 Manual
• ⚡ Unit test
• 💚 E2E

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue label.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[ryanfkeepers]

This is not a rotation, it's a randomization. We currently provide consistency between runs (theoretically) by binding each run to an account determined by the run ID, here: https://github.com/alcionai/corso/blob/main/.github/workflows/accSelector.yaml

Are we sure we want to drop this behavior to use a randomizer instead?

[HiteshRepo]

This is not a rotation, it's a randomization. We currently provide consistency between runs (theoretically) by binding each run to an account determined by the run ID, here: https://github.com/alcionai/corso/blob/main/.github/workflows/accSelector.yaml

Are we sure we want to drop this behavior to use a randomizer instead?

No @ryanfkeepers I am not sure about the solution. The real intention is to not change environment variables across test runs. Because changing env-vars are leading to tests not being cached