[Bug] Token cache serialization should expose their own options

[jmprieur]

Which Version of Microsoft Identity Web are you using ?
Microsoft Identity Web 0.1.5-preview

MsalMemoryTokenCacheProvider get its own options type but MsalDistributedTokenCacheAdapter injects IOptions<DistributedCacheEntryOptions> ?

microsoft-identity-web/src/Microsoft.Identity.Web/TokenCacheProviders/Distributed/MsalDistributedTokenCacheAdapter.cs

Line 38 in 17f48c6

IOptions<DistributedCacheEntryOptions> cacheOptions)

microsoft-identity-web/src/Microsoft.Identity.Web/TokenCacheProviders/InMemory/MsalMemoryTokenCacheProvider.cs

Line 39 in 17f48c6

IOptions<MsalMemoryTokenCacheOptions> cacheOptions)

It's historical and needs to be changed
We should not inject the IOptions<DistributedCacheEntryOptions> (because different components could be using different caches and would need to have different options)

What needs to be done?

• SessionTokenCache does not need option, it uses the session options
• MsalMemoryTokenCacheProvider.cs already has options, which we'll keep.
• Add a MsalDistributedTokenCacheAdapterOptions class inheriting from DistributedCacheEntryOptions, and use this one in lieu of DistributedCacheEntryOptions in MsalDistributedTokenCacheAdapter.cs (as other components would want to use the ASP.NET Core provided distributed cache)
• update the wiki documentation to mention the new option.

[jennyf19]

Included in 0.2.0-preview release