[PM-16789] introduce extension metadata

[audreyality]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-16789

📔 Objective

Refactor integration logic (@bitwarden/common/tools/integration) to improve code clarity and make extensions easier to comprehend.

Note: this logic is part of a larger work and split out for more efficient review. The logic that cuts over from the existing code to the new code will land at the end of these PRs.

🦖 System Evolution

The refactoring builds from "core" logic up to "domain" logic.

The core logic resides in 3 files:

• extension/data.ts - these are enum-alike data structures used to derive and conveniently access type information
• extension/type.ts - root data structures used to identify extensions and interact with extension data
• extension/metadata.ts - data derived from extension/data.ts that reifies the relationships among core data types.

Domain metadata then build on top of this:

• Site metadata - denotes a location open for extension.
• Vendor metadata - denotes the vendors that extend the password manager
  • Includes all forwarder vendors. At present this is hard-coded.
  • Also includes a "Bitwarden" vendor for use in test cases.
• Extension metadata - denotes an extension made by a vendor to a site.

There are two data-driven systems that manage the domain metadata:

• Extension registry - tracks the extensions that are live at any given moment
  • The extension must be registered. At present this is hard-coded.
  • The extension must not be prohibited by a rule. This is not presently in use.
• Extension site - runtime representation of the set of extensions available at a given site.

And there's an (unimplemented) service that exposes the extension sites to the systems they extend.

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – 114f9ed0-de23-4eca-8967-0dd00d0b1e4c

No New Or Fixed Issues Found