[Blazor] Update AuthenticationStateProvider to take advantage of Declarative persistent component state

[ilonatommy]

AuthenticationState serialization and deserialization uses declarative persistive component state

In order to solve the problem with non-matching keys in server and WASM:

[ComputeKey] inputString: Microsoft.AspNetCore.Components.WebAssembly.Server.AuthenticationStateSerializer.CurrentAuthenticationState, key: FxhcJRjzApOTVwAvYgWa1WBUHPHfWkmCIHP3kZeqZrM=
[Persist] type: Microsoft.AspNetCore.Components.WebAssembly.Server.AuthenticationStateSerializer, propertyType: Microsoft.AspNetCore.Components.Authorization.AuthenticationStateData, key: FxhcJRjzApOTVwAvYgWa1WBUHPHfWkmCIHP3kZeqZrM=, result: Microsoft.AspNetCore.Components.Authorization.AuthenticationStateData

MonoPlatform.ts:234 [ComputeKey] inputString: Microsoft.AspNetCore.Components.WebAssembly.Authentication.DeserializedAuthenticationStateProvider.CurrentAuthenticationState, key: CVLw9+XoagHLvt9DAe/VnpkOSQt34nib18t39RUYuuw=
MonoPlatform.ts:234 [Restore] type: Microsoft.AspNetCore.Components.WebAssembly.Authentication.DeserializedAuthenticationStateProvider, propertyType: Microsoft.AspNetCore.Components.Authorization.AuthenticationStateData, key: CVLw9+XoagHLvt9DAe/VnpkOSQt34nib18t39RUYuuw=, result: 

A cast to same class on registration was needed. To do that, both serializer and deserializer had to inherit from the same class, e.g. AuthenticationStateProvider.

Description of changes

• AuthenticationStateSerializer inherits now from AuthenticationStateProvider.
• Added registration of AuthenticationStateSerializer on the server side to save the state.
• Added registration of DeserializedAuthenticationStateProvider on the client side to restore the state.

Fixes #60718