chore: upgrade to dbt 1.8

[Jrmyy]

Description

Fixes #610

fix: remove table_owner retrieved from manifest
In DBT documentation, 2 owners are displayed: on the top line, we have the dbt owner as defined in the metadata, on the second line it is the owner of the sql representation of the model in Athena. But Athena does not support table owner except if used with LakeFormation. But in any case it is not an owner, in a traditional way as we can see it in Postgres. Since dbt 1.8 remove the ability to use the manifest object when retrieving catalog or schemas, we were forced to remove it. But it feels like we can remove it now because we have an owner displayed and the documentation and it reflects more what happened in reality.

Checklist

• You followed contributing section
• You kept your Pull Request small and focused on a single feature or bug fix.
• You added unit testing when necessary
• You added functional testing when necessary

[nicor88]

Overall looks good.

dbt is still releasing new beta versions, see this https://github.com/dbt-labs/dbt-core/releases/tag/v1.8.0b2.

My main question is: shall we consider to merge and release this and keep updating based on beta/final release? or we keep this open till the final release is reached?

[Jrmyy]

If we follow what other adapters did, they all merged and release beta versions, so we might want to also do that.

It makes things trickier to deploy hotfixes (targeting commits or a v1.7 branch) but it will also let more time to stress test the beta version of production-grade projects

[nicor88]

Others adapters have people and resources to allocate to dbt. If we find time to keep up with the dbt 1.8 pre-, releases, I'm fine to merge it already.
@svdimchenko wdyt?

[svdimchenko]

Others adapters have people and resources to allocate to dbt. If we find time to keep up with the dbt 1.8 pre-, releases, I'm fine to merge it already. @svdimchenko wdyt?

I believe we should create v1.7 branch as @Jrmyy mentioned to be able do hotfixes on previous dbt version. I'm not sure if other dbt-dependent projects will upgrade to 1.8 smoothly as well (like elementary)

I've created v1.7 branch. Now I believe we are ready to go

[nicor88]

@svdimchenko I don't see much sense of creating another branch tbh, as it will just create more extra work.
Let's use KISS, we target the main branch and we keep releasing periodically based on the beta release, given community contributions that target main will be way easier to maintain.

The good part of 1.8,it is that we don't have to follow anymore dbt semantic library versioning. so we are starting to become free on the semantic library version of the adapter.

Said so, I'm in favor of merging this, and do a release. cc @Jrmyy