[CT-2525] Begin "basic" parsing of SemanticModel to the Manifest as nodes

[QMalcolm]

In #7499 we defined dbt-core's representation of a Semantic node. In #7456 we defined the the expected YAML representation of a SemanticModel. This issue is to begin parsing SemanticModels defined in YAML to SemanticModel nodes on the Manifest. We do have a prototype of one way this could be done, #7187, if inspiration is needed.

SemanticModel node parsing is slight more complicated than Metric Parsing (#7501) in that additional nodes can be created. Specifically if a Measure on the SemanticModel is defined with create_metric: true then a Metric Node should be created for the measure. This issue IS NOT expected to handle that edge case. We have a separate issue, #7504, for tackling that specific issue.

Blocked by:

• [CT-2521] Define SemanticModel node for the Manifest #7499

[jtcohen6]

During ref resolution (end of parsing), we will need to include an object representing the resolved relation for the model that the SemanticModel is referencing, via model: ref('something').

We should include an object that contains:

• relation path components (database, schema, identifier)
• stringified relation_name, which will already apply quoting + include policies that vary by adapter (e.g. "schema"."identifier")

If a SemanticModel references a disabled model, raise an error :)