[release/10.0] Allow UserStore to update passkey name

[github-actions]

Backport of #63981 to release/10.0

/cc @MackinnonBuck

Allow UserStore to update passkey name

Fixes an issue where UserStore cannot apply updates to a passkey's name after its initial creation.

Description

Microsoft.AspNetCore.Identity.EntityFrameworkCore provides UserStore (users + roles), and UserOnlyStore (users only). Both stores enable associating one or more passkeys with a user. Passkeys are a new feature in .NET 10.

The UserPasskeyInfo type contains information about a passkey, including its ID, the public key, and the display name (Name).

Some properties in UserPasskeyInfo are mutable, and others are immutable. Calling UserManager.AddOrUpdatePasskeyAsync(user, passkey) will either add a passkey to the user or update only the mutable properties of an existing passkey. These mutable properties consist solely of:

• Name
• SignCount
• IsUserVerified
• IsBackedUp

The underlying store implementation controls how these properties get updated. UserOnlyStore correctly handled mutations to each of these properties, but UserStore did not update the Name property.

This PR fixes UserStore so that the Name property gets correctly updated.

Fixes #63923

Customer Impact

Apps that utilize Microsoft.AspNetCore.Identity.EntityFrameworkCore and support roles will not be able to change the name of a passkey after its initial creation. A workaround exists, which is to create a custom store type that extends UserStore and override the AddOrUpdatePasskeyAsync method to exhibit the correct behavior.

Regression?

• Yes
• No

Passkeys are a new feature in .NET 10. The feature never previously worked in this code path.

Risk

• High
• Medium
• Low

The fix is simple: copy an additional property that wasn't getting copied. This is not a breaking change and does not require schema changes or database migrations.

Verification

• Manual (required)
• Automated

New automated tests have been added to ensure that all store implementations support modifications to all mutable passkey properties.

Packaging changes reviewed?

• Yes
• No
• N/A

[wtgodbe]

@MackinnonBuck there are some test failures here that look potentially real

[MackinnonBuck]

@wtgodbe These tests are flaky. For some reason, the database is getting initialized with the wrong schema occasionally. I'm investigating this in #64019