[Key Connector] Add support for key connector and OTP

[eliykat]

Type of change

• Bug fix
• New feature development
• Tech debt (refactoring, code cleanup, dependency upgrades, etc)
• Build/deploy pipeline (DevOps)
• Other

Objective

Add support for user verification using OTP instead of master password. Required to support the crypto agent.

Equivalent changes in web for reference: bitwarden/web#1256.

Code changes

• src/background/main.background.ts - add KeyConnectorService, update deps
• src/popup/accounts/remove-password.component.(html|ts) - add remove password component - browser needs its own template, it otherwise just uses the jslib base class
• src/popup/accounts/sso.component.ts - this onSuccessfulLogin callback runs after the user successfully authenticates with SSO. Currently, this refreshes all open tabs/windows belonging to the extension - I'm not sure why, but I assume it's so that it'll display the unlock page properly. With Key Connector, the user is already unlocked and all this does is dump the keys out of memory, locking the vault again. So: don't refresh if the vault is already unlocked.
• src/popup/app-routing.module.ts - update routing to include remove-password.component.
• src/popup/app.component.ts - receives the convertAccountToKeyConnector message sent by syncService. However, sync occurs in the background, so we need some way to persist this message when the user opens the popup. We do this by saving to storageService and checking for it in the CanActivate guard (which is in the jslib PR). If it's detected by CanActivate, then the user is taken to the remove password component.
• src/popup/app.module.ts - update components, order components alphabetically
• src/popup/settings/export.component.html - update to use VerifyMasterPasswordComponent if required (which adds OTP support), update to use reactive forms (per changes in jslib)
• src/popup/settings/settings.component.(html|ts) - hide "Change Master Password" if using Key Connector
• src/popup/vault/add-edit.component.(html|ts) - hide "Master Password Reprompt" option if using Key Connector

Screenshots

@Hinton can you please provide?

Testing requirements

General testing requirements for crypto-agent changes to be provided to QA.

Before you submit

• I have checked for linting errors (npm run lint) (required)
• This change requires a documentation update (notify the documentation team)
• This change has particular deployment requirements (notify the DevOps team)

[eliykat]

@Hinton a couple of comments below. Nice solution to the 'state' problem I think.

• Did you mean to bump jslib on this branch before the jslib PR is merged?