[PM-5744] Adjust Fido2 Content Script Injection to Meet mv3 Requirements

[cagonzalezcs]

Type of change

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

Objective

The changes in this PR ensure that we can inject the FIDO2 content scripts used for the Passkeys feature in a manner than is allowed within manifest v3. It also addresses a couple of side concerns that ensure we inject our content scripts for this feature in a manner that is respectful of user settings while ensuring we can inject them ASAP.

With these changes, we are introducing a polyfill that facilitates the browser.contentScripts.register method within browsers that do not support this feature (Chrome and Safari). This allows us to dynamically register content scripts such that we can handle injecting the FIDO2 content scripts without any delay, allowing us to more effectively introduce the WebAuthn overrides to facilitate Bitwarden passkeys behavior. With this added polyfill, we can also disable the content scripts entirely for users who do not wish to use the feature. This ensures that we do not inject these scripts at all if the user does not want them injected into a tab.

Another improvement introduced by this PR is the lightening of the page-script.js file that gets injected to facilitate Passkeys behavior. We've reworked the imports used in this script to have the script go from ~650kb to ~35kb after compilation.

Finally, we've implemented a fix that ensures we dynamically inject or disable the FIDO2 content scripts after a user has set/unset the setting for passkeys. This ensures that users do not need to reload their browser in order to use the feature after the setting has been turned on. It also disables the feature in all existing browser tabs if the user has turned the feature off.

Code changes

I'm going to reference files that directly affect the implementation, anything not referenced either represents testing files, abstractions, or other small changes that do not affect the implementation in a significant manner.

• apps/browser/src/autofill/content/autofill-init.ts: Fixing a small issue here where can get a Extension context invalidated error due to a delayed capture of autofill page content if the user reloads the extension
• apps/browser/src/background/main.background.ts: Adjusting the implementation of the main background to rename all references to the Fido2Service class such that the referenced the new Fido2Background class used to handle background interactions for Fido2 behavior.
• apps/browser/src/background/runtime.background.ts: Adjusting the implementation of RuntimeBackground to bring all Fido2 related messages to the Fido2Background. This will centralize expected logic triggered by the message within Fido2Background.
• apps/browser/src/manifest.json: Removing the set trigger-fido2-content-script-inject.js static content script in favor of the dynamic registration approach we now use. Also adding the webNavigation permission to facilitate dynamic registration of these scripts in all frames.
• apps/browser/src/manifest.v3.json: Removing the set trigger-fido2-content-script-inject.js static content script in favor of the dynamic registration approach we now use. Also adding the webNavigation permission to facilitate dynamic registration of these scripts in all frames.
• apps/browser/src/platform/browser/browser-api.register-content-scripts-polyfill.ts: This is a newly introduced polyfill that allows us to dynamically register static content scripts within the extension. We use this to ensure we do not inject the Fido2 content scripts into the tabs of users who do not wish to use the feature. The reason we are incorporating this directly rather than through the npm package is due to the structure of the package. It throws several errors during compilation and when jest testing the implementation. As a result, it makes sense to "fork" the package into our implementation and maintain it ourselves. I've added typing information for this, as well as refactored the implementation to ensure we do not enable it's logic unless necessary.
• apps/browser/src/platform/browser/browser-api.ts: Adding methods that allow us to dynamically register static content scripts using either the chrome.scripting API, the browser.contentScripts API, or the content script polyfill depending on what is available to use in the browser scope.
• apps/browser/src/vault/fido2/background/fido2.background.ts: This is a rework of the Fido2Service class that now facilitates injection of the Fido2 content scripts and updating behavior related to Fido2 script injection. This class now handles all Fido2 related extension messages, and triggers behavior as necessary based on those messages.
• apps/browser/src/vault/fido2/content/content-script.ts: Refactoring the implementation of the core Fido2 content script and ensuring that it can tear down its logic if necessary.
• apps/browser/src/vault/fido2/content/messaging/messenger.ts: Refactoring small elements in this implementation to ensure that our Fido2 implementation follows the WebAuthn specifications more closely.
• apps/browser/src/vault/fido2/content/page-script-append.mv2.ts: This is a content script used specifically for manifest v2 which facilitates injection of the fido2 content script through appending the script to the DOM. This approach will not be allowed in mv3, but is the only way to trigger the page-script.js injection in mv2.
• apps/browser/src/vault/fido2/content/page-script.ts: Refactoring the implementation to ensure that the script can tear down its logic in the case that it needs to do so.
• apps/browser/webpack.config.js: Updating the webpack implementation to ensure that we conditionally create the content script that appends page-script.js to the DOM.
• libs/common/src/vault/services/fido2/fido2-client.service.ts: Updating the implementation of isFido2FeatureEnabled to ensure we disqualify usage of the feature as soon as possible.
• libs/common/src/vault/services/fido2/fido2-utils.ts: Removing the reference to the platform Utils lib and pulling used methods from that lib into this file. This is done to lighten the load of page-script.ts

[coroiu]

🔥