[PM-16788] revise generator metadata

[audreyality]

🎟️ Tracking

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

📔 Objective

Refactor generator metadata (data and type folders in @bitwarden/generator-core) to improve code clarity and make the dependencies easier to follow.

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 several files:

• metadata/data.ts - these are enum-alike data structures used to derive and conveniently access type information
• metadata/type.ts - root data structures used to identify extensions and interact with extension data

Domain metadata then build on top of this:

• Algorithm metadata - describes algorithms and capabilities
• Profile metadata - describes a use-case for the generator
  • At present all generators share the "account" profile.
  • This was introduced to enable a secondary profile for master password generation.
  • Profiles also enable settings to be provided by the generator ("core") or to be delegated to a secondary system. The first use-case enables the extension system to provide settings (future PR). It could also be used to create collection-bound or autofill-provided profiles.
• Generator metadata - combines algorithm metadata, profile metadata, and engine creation logic for use by the credential generator service.

At present there isn't a system managing this data; it's all hard-coded in email,
password, and username subfolders. Management systems will be introduced in a
followup PR.

🦮 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