Passkey last_login Can't be Disabled

[alexclst]

In Statamic 6 passkeys were added. They're stored in user yaml files. They include a piece of metadata that is last_login that is changed every time they are used to save the timestamp of last use. This is a problem when users are being tracked with Git, as every passkey log in will change a user's file. We want users tracked in Git since we want the same users on multiple instances of a site (live, staging, locals) as content edits are attributed to them, but having this last_login in that same file is going to cause too many Git-tracked changes for these files.

Can there be a way to disable last_login saving to avoid this situation? Or to move that to a different set of files we can ignore from Git?

[efc]

More generally, it would be great if Statamic could separate the public user info (basic profile information) from the secret user information (things like password hash and this last_login for passkeys), so that we could allow git to include the information that is needed to do things like attribute authorship of posts properly, but could keep private data off git.