SharedTokenCacheCredential uses MSAL

[chlowell]

SharedTokenCacheCredential must handle its cache as MSAL does because that cache is shared by applications accessing it through MSAL. The current approach, duplicating MSAL Python's logic as needed, is fragile and error prone, and adds considerable complexity. It would be better for the credential to access the cache through MSAL.

For the async SharedTokenCacheCredential, this is blocked by AzureAD/microsoft-authentication-library-for-python#88.

[chlowell]

#13490 made this change to the sync credential.

[github-actions]

Hi @chlowell, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.