Add Parsed class for new-style YAML Metric

[theyostalservice]

Resolves LINEAR JIRA

Depends on #12157and #12395

Problem

We need to actually parse and process the new YAML for metrics (introduced in #12157 ). You can see this file for the schema agreed on for V2 Semantic YAML here and already implemented in fusion.

This PR will deal with ONLY parsing metrics that are found outside of semantic models. Parsing those actually on semantic models will require slightly more work on top of this.

Solution

Similar to several other recent PRs, I break the the Metric parsing up wherever I can easily do so. Unlike earlier PRs, I don't break apart the processing code for dependencies because it's a little complex and stuck inside manifest.py, and I'd rather do any breaking up of that file in its own separate PR if we decide its necessary.

Checklist

• I have read the contributing guide and understand what's expected of me.
• I have run this code in development, and it appears to resolve the stated issue.
• This PR includes tests, or tests are not required or relevant for this PR.
• This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
• This PR includes type annotations for new and modified functions.

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[theyostalservice]

• Add derived_semantics.entities to models #12401
• Parse metrics on models #12397
• Add Parsed class for new-style YAML Metric #12161 👈 (View in Graphite)
• Add Semantic entities to columns for new YAML #12395
• Add new-syle YAML unparsed metric #12157
• Parse dimensions defined on dbt columns into a semantic model #12386
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codecov]

Codecov Report

❌ Patch coverage is 76.10619% with 27 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.29%. Comparing base (db5a9e0) to head (65e0bfc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12161      +/-   ##
==========================================
- Coverage   91.41%   91.29%   -0.13%     
==========================================
  Files         203      203              
  Lines       25207    25282      +75     
==========================================
+ Hits        23044    23081      +37     
- Misses       2163     2201      +38     

Flag	Coverage Δ
integration	88.12% <75.22%> (-0.20%)	⬇️
unit	65.20% <26.54%> (-0.14%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Unit Tests	65.20% <26.54%> (-0.14%)	⬇️
Integration Tests	88.12% <75.22%> (-0.20%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Additional Artifact Review Required

Changes to artifact directory files requires at least 2 approvals from core team members.

The base branch was changed.

[QMalcolm]

Bypassing because the checks all passed, and we just dropped duplicate commits 🙈