Incorrect Server Endpoint Saved to Account Profile

### Steps To Reproduce

1. Go to 'Add account'
2. Select 'Self-Hosted' and enter a self-hosted server URL and continue to the Master password login
3. Autofill the 'Master password' field using an account whose vault is stored on vault.bitwarden.com
4. Unlock the vault
5. View the saved account profiles, the self-hosted server account is saved under 'vault.bitwarden.com'

### Expected Result

The self-hosted server account should save the self-hosted server URL

### Actual Result

The self-hosted server account is saved under 'vault.bitwarden.com'

### Screenshots or Videos

_No response_

### Additional Context

The correct self-hosted server URL is saved to the account if the master password is entered manually rather than using autofill.

The initial login session on the self-hosted server account appears to connect fine, further vault unlocks lead to the message "An error has occurred." if any vault changes are made.

### Build Version

2025.3.0 (2034)

### What server are you connecting to?

US

### Self-host Server Version

_No response_

### Environment Details

- Device: iPad Pro M4
- OS Version: 18.3.2

### Issue Tracking Info

- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Start by reproducing the Add account flow on iPad using autofill with a vault.bitwarden.com account, then compare it with manual master-password entry. Trace where the self-hosted server URL and saved account profile are set; done means the self-hosted URL remains associated with the account and subsequent vault unlocks do not fail after changes.

Written by the indexing model from the issue text.