dbt updates + test coverage

[bmos]

dbt is an important database component, but we had no tests for how we integrate with it.
Closes #1332

What's Changed

• Created basic dbt test suite
  • Integration tests to watch for changes to dbt api/enum structures
  • Tests for dbtRunnerParsons wrapper class
  • Tests for Manifest class data processing, filtering, and getattr behavior
  • Tests for generating markdown output with appropriate emoji
• Added placeholder test files for dbt submodules
• Updated dbt/models.py and dbt/logging.py to handle skipped and failed statuses (introducing blue circle for skipped status)
• Updated dbt/models.py and dbt/logging.py to utilize NodeStatus Enum rather than hardcoded strings
• Updated dbt/logging.py to directly use emoji characters (defined once) rather than unicode for readability
• Updated dbt/logging.py to use f strings and more concise logic

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
parsons/utilities/dbt
__init__.py
dbt.py
logging.py
models.py					24-26
Project Total

This report was generated by python-coverage-comment-action

[bmos]

@austinweisgrau The type hint change of dbt_manifest from dbtManifest to ExecutionResult is the primary thing I need your input on here.
It silenced a ton of "method not found" errors in my IDE which seemed to indicate that it was mistyped, but I don't know much about dbt to say for sure.
If it was mistyped, the variable name should probably be changed too.