Add ClaimData for AuthenticationStateData and fix overtrimming

[halter73]

This PR is a follow up to #55821 which added the AuthenticationStateProvider implementations from the .NET 8 Blazor web project templates to the runtime. You can opt into using these by adding the new services as follows.

// Server Program.cs
builder.Services.AddRazorComponents()
    .AddInteractiveWebAssemblyComponents()
    .AddAuthenticationStateSerialization();

// Client Program.cs
builder.Services.AddAuthenticationStateDeserialization();

These services rely on JSON serializing and deserializing the newly added AuthenticationStateData type which previously contained a Claims property of type IList<KeyValuePair<string, string>>. After API review feedback in #52769, we've decided to update AuthenticationStateData.Claims to be an IList<ClaimData>.

This PR also fixes #56207 which was caused by the overtrimming AuthenticationStateData.Claims and updates the ServerRenderedAuthenticationStateTest and DefaultAuthenticationStateSerializationOptionsTest to test published trimmed WebAssembly static assets.

As part of this, I refactored the common logic of most tests that currently use static assets published to the "trimmed-or-threading" to use the new TrimmingServerFixture. However, I wonder if we should go further and make BasicTestAppServerSiteFixture use trimmed static assets by default when TestTrimmedOrMultithreadingApps is configured.

Fixes #52769
Fixes #56207

[halter73]

@dotnet/aspnet-blazor-eng I'm curious what everyone thinks about this.

[javiercn]

I would say that if other tests don't break, we could enable it, but I suspect we wanted to have this isolated. I believe in the past we would test all the apps with trimming during release. I don't know if/when that changed, but I'm ok if we bring that back.

[amcasey]

Product change LGTM. I'll let the stakeholders figure out the test infra changes.