flags & tracking from dbt/artifacts

[emmyoop]

resolves #9390

Problem

dbt.tracking and dbt.flags from dbt/artifacts/schemas/manifest.py represent a dependency on dbt internals from an upstream component, meaning we could never package it separately.

Solution

Use global values instead of replying on post_init. Fix tests to account for new pattern.

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

[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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.98%. Comparing base (7df747a) to head (daf4c49).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9628      +/-   ##
==========================================
- Coverage   88.00%   87.98%   -0.02%     
==========================================
  Files         176      176              
  Lines       22311    22309       -2     
==========================================
- Hits        19634    19628       -6     
- Misses       2677     2681       +4     

Flag	Coverage Δ
integration	85.57% <100.00%> (-0.02%)	⬇️
unit	62.10% <100.00%> (-0.01%)	⬇️

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.

[gshank]

Looks good