In-memory/production distributed caches

[guardrex]

Fixes #35494

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/call-web-api.md	aspnetcore/blazor/call-web-api
aspnetcore/blazor/fundamentals/signalr.md	aspnetcore/blazor/fundamentals/signalr
aspnetcore/blazor/security/blazor-web-app-with-entra.md	aspnetcore/blazor/security/blazor-web-app-with-entra

[halter73]

Should we also show setting MsalDistributedTokenCacheAdapterOptions.Encrypt = true so the access tokens are data protected at rest? Of course, then we have to link to content about managing data protection keys. But if we're already asking you to manage a distributed cache, that feels like a similar level of complexity.

@blowdart @GrabYourPitchforks

[guardrex]

The PR is updated with ...

• The MSAL token cache options (encrypt, sliding period, etc.).
• Shared DP key ring with Azure Blob Storage and Key Vault as the example.
• Remarks on how to just use an in-memory provider and unencrypted tokens during early development and testing.

The companion PR that updates the sample apps is also ready at dotnet/blazor-samples#544.