Move Exposure data parts to dbt/artifacts

[QMalcolm]

resolves #9380

Problem

We are moving data artifacts to dbt/artifacts in a piecewise fashion. We needed to move Exposure as part of that.

Solution

Moved data portion of Exposure to dbt/artifacts (and all other classes that doing so required)

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/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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0836095) 87.97% compared to head (5a9145a) 88.01%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9494      +/-   ##
==========================================
+ Coverage   87.97%   88.01%   +0.04%     
==========================================
  Files         166      167       +1     
  Lines       22119    22130      +11     
==========================================
+ Hits        19459    19478      +19     
+ Misses       2660     2652       -8     

Flag	Coverage Δ
integration	85.56% <100.00%> (+0.12%)	⬆️
unit	62.36% <97.67%> (+0.02%)	⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MichelleArk]

🧼

[QMalcolm]

The branch for this PR was based off of the branch qmalcolm--9387-move-semantic-model-to-dbt-artifacts (now deleted) which was the branch for the PR #9485. Because we only allow for squash merges, the commits from the branch qmalcolm--9387-move-semantic-model-to-dbt-artifacts don't exist on main, but instead a single commit exists with all the contents. Thus this PR now has merge conflicts 😞 So I'm now going to rebase this branch off of main (which will make it look like the approval came before the work was done, but that's not actually the case).