Fix adapter reset race condition in lib.py

[drewbanin]

resolves #5919

Description

This PR updates the lib.py file to avoid mutating global adapter state when generating a RuntimeConfig. This logic was once necessary in order to work around issues with dbt deps, though it's fairly clear at this point that we'll need to employ a radically different approach for deps in the future (including higher-order, first-class APIs). In the meantime, this change fixes possible race conditions for concurrent callers of get_dbt_config

Additional changes:

• Change RuntimeArgs from a namedtuple to a dataclass fix an error in dbt v1.3.x (via this PR, i think)
• Tweaked / fixed up code comments :)
• Made it possible to control manifest sql operation nodes names. Historically, they've been hard-coded to "name". The default value is query for backwards compatibility. Just added an optional arg for this

TODO:

• write tests (would love guidance on the best place to test this! Not sure that we want/need to repro the race condition, but a couple of tests for lib.py would be dope here)
• figure out how to run changie again
• almost positive black and flake8 are going to yell at me

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• 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
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

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

[gshank]

I agree that at some point it would be good to have tests for lib.py. I'm not exactly sure what they'd look like though. I'm okay with doing that as a separate effort.

[github-actions]

The backport to 1.0.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.0.latest 1.0.latest
# Navigate to the new working tree
cd .worktrees/backport-1.0.latest
# Create a new branch
git switch --create backport-5921-to-1.0.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4e8aa007cf17fff7605df1bb38eda2842dc9ba50
# Push it to GitHub
git push --set-upstream origin backport-5921-to-1.0.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.0.latest

Then, create a pull request where the base branch is 1.0.latest and the compare/head branch is backport-5921-to-1.0.latest.