Add storeInCache request parameter to control which tokens are persisted to the cache

[tnorling]

Adds new request parameter to control which tokens should be stored in the cache. This will give us more flexibility and enable our 1P library to use our public APIs rather than depend on and/or re-implement internal implementation details.

Note: msal-node is out of scope for this change for now. If there's a need to extend this feature to node in the future the param can be removed from the "Omit" list of the request types and tests added.

[codecov-commenter]

Codecov Report

Merging #6248 (f53ef12) into dev (81d34b4) will decrease coverage by 1.07%.
Report is 222 commits behind head on dev.
The diff coverage is 67.42%.

Flag	Coverage Δ
msal-angular	96.73% <92.78%> (+0.22%)	⬆️
msal-browser	85.69% <ø> (-0.78%)	⬇️
msal-common	?
msal-core	?
msal-node	?
msal-node-extensions	68.51% <60.77%> (-7.13%)	⬇️
msal-react	?
node-token-validation	?

Files Changed	Coverage Δ
...ions/msal-node-extensions/src/utils/Environment.ts	20.51% <0.00%> (-22.08%)	⬇️
lib/msal-angular/src/msal.interceptor.ts	100.00% <ø> (ø)
lib/msal-angular/src/msal.module.ts	100.00% <ø> (ø)
lib/msal-angular/src/msal.navigation.client.ts	93.33% <ø> (+0.47%)	⬆️
lib/msal-angular/src/msal.redirect.component.ts	100.00% <ø> (ø)
lib/msal-angular/src/msal.service.ts	100.00% <ø> (ø)
lib/msal-angular/src/packageMetadata.ts	100.00% <ø> (ø)
...b/msal-browser/src/app/IPublicClientApplication.ts	43.75% <ø> (ø)
...ib/msal-browser/src/app/PublicClientApplication.ts	66.66% <ø> (-28.67%)	⬇️
...er/src/broker/nativeBroker/NativeMessageHandler.ts	86.29% <ø> (+0.33%)	⬆️
... and 67 more

... and 165 files with indirect coverage changes

[hectormmg]

LGTM

[lalimasharda]

LGTM!

[peterzenz]

How does this work with WAM/Native Brokers? If the app experience is going to be very different between a pure browser flow and a JS/Native flow because of this, then I'd suggest we back this change out.

[tnorling]

How does this work with WAM/Native Brokers? If the app experience is going to be very different between a pure browser flow and a JS/Native flow because of this, then I'd suggest we back this change out.

This is referring to the local MSAL cache (browser storage) and applies regardless of where the token came from. I'm not the biggest fan of the parameter name myself but if you have suggestions for making this clearer or an alternative solution let me know.