feat(FIR-35169): dbt 1.8 support

[ptiurin]

Resolves #124

Description

DBT 1.8 support with refactors required and new tests. Some imports have changed as well as interfaces.
We no longer need to pin the dbt-core version, but need to make sure dbt-adapters module is included.

Checklist

• 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 run changie new and committed everything in .changes folder
• I have removed any print or log calls that were added for debugging.
• I have verified that this PR contains only code changes relevant to this PR.
• If further integration tests are now passing I've edited tests/functional/adapter/* to account for this.
• I have pulled/merged from the main branch if there are merge conflicts.
• After pulling/merging main I have run pytest on the included or updated tests/functional/adapter/.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[stepansergeevitch]

LGTM, one question

[stepansergeevitch]

Is this one about reverting the last operation or about canceling the ongoing query? Can we implement this if latter?

[ptiurin]

I believe this is about cancelling the last executed query. As discussed, we can do it in a roundabout way by sending a termination signal to a process that's running a query, but this is a very ugly approach to it and I'm not even sure if there's an interest in using this method. It's very niche in the context of DBT.
For reference, postgres and snowflake implementations have a server-side cancel here.