Use glue APIs instead of information schema

[nicor88]

Based on #4 (comment)

Implementation should be covered here northvolt/dbt-athena@49c7111

Using Glue API is better as faster and should allow multi-threading.

TODO

• Use glue api instead of information schema
• Use delete table from glue api - consider to do for Iceberg as well, as timeout lead to not having full deleted data. Before dropping pick the location from glue catalog.

[nicor88]

@jessedobbelaere FYI.

[chrischin478]

@nicor88 I'll make an attempt at the Glue API delete

[Jrmyy]

👋🏻 Hello @chrischin478
Have you been able to work on this issue ?
Otherwise, if don't have time, I can take since I developed the part of about table info 🙂 .

[chrischin478]

@Jrmyy still giving it a crack. When should this be completed by? I don't want to take too long with this.

[nicor88]

we are planning to close this for the 1.4.4 milestone, that should happen in the next week.

[chrischin478]

@Jrmyy if I haven't made significant progress by end of day 4/23, will that give you enough time to complete the feature before the milestone?