Destination postgres: add option for cascade drop

[edgao]

closes #35386

• AbstractJdbcDestinations.getSqlGenerator now accepts config: JsonNode
• JdbcSqlGenerator now accepts cascadeDrop: Boolean = false, and adds cascade() to its drop table statements
  • there are three of these; I only modified two of them (the ones that drop the final table). The v1v2 migration drops the v2 raw table if it already exists, which IMO if we need to cascade drop, then something is wrong. The v1v2 migration shouldn't even be triggering if the user is already building stuff on top of v2 tables, because it should only run if the v2 tables don't exist.
• Add a testcase to the postgres sqlgenerator integration test to verify cascade works (tested locally to verify that the old code fails the test)

I didn't do any manual syncs/etc, lmk if you want that, or e.g. want a screenshot of the config option, etc

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 11, 2024 6:30pm

[gisripa]

lgtm.

Add a doc update in postgres.md with big :::caution 😅

[edgao]

/publish-java-cdk

🕑 https://github.com/airbytehq/airbyte/actions/runs/8651263369
✅ Successfully published Java CDK version=0.30.0!