fix: edge case fix on iceberg target table being dropped instead on being renamed first

[nicor88]

Description

See https://getdbt.slack.com/archives/C013MLFR7BQ/p1717497450266499

Pretty much https://github.com/dbt-athena/dbt-athena/pull/625 introduced a regression that was not letting iceberg working in an full high available mode. This PR cover the issue, and add functional tests to catch these edge case. Plus it introduce some improvements that allow to work properly in some restrictive LF permission models, where drop can happen only on existing objects.

Models used to test - Optional

See functional tests

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]

@octiva might give some input here, as he has a LF env with restricted policies, and we want to be sure that all works fine.

[nicor88]

@octiva it will be good if you can test this feature again in your environment to see if all works as expected. Thanks.

@Avinash-1394 I hope that I cover and addressed your question/suggestion. Feel free to have a look.