[release/7.0] [Blazor] Fix linking issues (#44260)

Backport of #43515 to release/7.0

/cc @MackinnonBuck @javiercn

# Fix linking issues

Fixes an issue reported by manual testing where Blazor WebAssembly projects created from the Individual Auth template throw an exception on page load after publishing.

## Description

The problem was already fixed in `main` by making `RemoteAuthenticationService` more linker friendly. From @javiercn's comment on the original issue:

> What was happening was that the linker was erasing the parameter names of the record we were using for serializing the data

Fixes https://github.com/aspnet/AspNetCore-ManualTests/issues/1556

## Customer Impact

Customers are likely to encounter this issue, especially since one of our project templates reproduces the bug. It's expected that our project templates should be ready to publish out of the box.

## Regression?

- [X] Yes
- [ ] No

Regressed from .NET 6.

## Risk

- [ ] High
- [ ] Medium
- [X] Low

The change only involves minor restructuring to enable linker-friendliness. There are no changes to any core functionality.

## Verification

- [X] Manual (required)
- [ ] Automated

## Packaging changes reviewed?

- [ ] Yes
- [ ] No
- [X] N/A

Author: github-actions[bot]

src/Components/WebAssembly/WebAssembly.Authentication/src/Services/RemoteAuthenticationService.cs

@@ -31,7 +31,7 @@ public class RemoteAuthenticationService<
 {
     private static readonly TimeSpan _userCacheRefreshInterval = TimeSpan.FromSeconds(60);
     private bool _initialized;
-    private readonly JavaScriptLoggingOptions _loggingOptions;
+    private readonly RemoteAuthenticationServiceJavaScriptLoggingOptions _loggingOptions;
 
     // This defaults to 1/1/1970
     private DateTimeOffset _userLastCheck = DateTimeOffset.FromUnixTimeSeconds(0);
@@ -93,7 +93,11 @@ public RemoteAuthenticationService(
         Navigation = navigation;
         AccountClaimsPrincipalFactory = accountClaimsPrincipalFactory;
         Options = options.Value;
-        _loggingOptions = new JavaScriptLoggingOptions(logger?.IsEnabled(LogLevel.Debug) ?? false, logger?.IsEnabled(LogLevel.Trace) ?? false);
+        _loggingOptions = new RemoteAuthenticationServiceJavaScriptLoggingOptions
+        {
+            DebugEnabled = logger?.IsEnabled(LogLevel.Debug) ?? false,
+            TraceEnabled = logger?.IsEnabled(LogLevel.Trace) ?? false
+        };
     }
 
     /// <inheritdoc />
@@ -163,6 +167,7 @@ public virtual async ValueTask<AccessTokenResult> RequestAccessToken()
     /// <inheritdoc />
     [DynamicDependency(JsonSerialized, typeof(AccessToken))]
     [DynamicDependency(JsonSerialized, typeof(AccessTokenRequestOptions))]
+
     public virtual async ValueTask<AccessTokenResult> RequestAccessToken(AccessTokenRequestOptions options)
     {
         if (options is null)
@@ -215,6 +220,7 @@ protected internal virtual async ValueTask<ClaimsPrincipal> GetAuthenticatedUser
         return user;
     }
 
+    [DynamicDependency(JsonSerialized, typeof(RemoteAuthenticationServiceJavaScriptLoggingOptions))]
     private async ValueTask EnsureAuthService()
     {
         if (!_initialized)
@@ -240,7 +246,15 @@ private void UpdateUser(Task<ClaimsPrincipal> task)
         static async Task<AuthenticationState> UpdateAuthenticationState(Task<ClaimsPrincipal> futureUser) => new AuthenticationState(await futureUser);
     }
 
-    private record JavaScriptLoggingOptions(bool DebugEnabled, bool TraceEnabled);
+}
+
+// We need to do this as it can't be nested inside RemoteAuthenticationService because
+// it needs to be put in an attribute for linking purposes and that can't be an open generic type.
+internal class RemoteAuthenticationServiceJavaScriptLoggingOptions
+{
+    public bool DebugEnabled { get; set; }
+
+    public bool TraceEnabled { get; set; }
 }
 
 // Internal for testing purposes