Chore/credential migration

[RubenSmn]

New version of storing the credentials. Allows for storing the whole URL including, protocols and all subdomains.

The Migrator will run on startup check the version of the built-in store and updates the credentials to the new format if necessary.

For the migration it will

• check if a url matches any in the history, if yes, use that url, else
• check if the url already has a protocol if not, add https:// protocol
• finally store the new credentials and update the version

The same is done for the credentials that should never be saved

I've used the origin property of the URL since this one gives us the whole 'base' url so we don't need extra fields to save the protocol and subdomains.

[PalmerAL]

Thanks, I think this approach looks good generally. I haven't fully tested this yet, but a couple of initial comments:

• In the keychain import, the saved field is this: domain: new URL(domainWithProtocol).origin,, but in the migrator, the equivalent field is url: historyEntry.url. Is your intent to save an origin or a complete page URL? (I think origin should be fine)
• Doing this isn't secure: matchHost.replace('www.', '') === domain || matchHost === domain - imagine comparing "example.com" and "example.www.com". The www should be removed only if it appears at the start, immediately after a protocol.
• We'll need a change for Bitwarden as well (like I did here).