Update the Flyway plugin for YugabyteDB

[Sfurti-yb]

Problems:

• The current implementation does not use jdbc:yugabytedb:// for the connections.
• If user is using Flyway baseline, the baseline has default implementation of putting DDL and DML in a single transaction which YB will roll back the DML because of the catalog version changes.
• For YugabyteDB v2.20 all the commands fail with the error: ERROR: advisory locks are not yet implemented which has not been an issue for previous versions and not errored out.

Solutions:

• Added jdbc:yugabytedb: protocol in YugabyteDBDatabaseType.java
• Changed the implementation of getRawCreateScript() so that DDLs and DMLs are not in a single transaction
• For the pg_advisory_lock issue, setting yb_silence_advisory_locks_not_supported_error=on where connection is create and returning that connection

Tests: The tests for these changes are in the repository: https://github.com/yugabyte/flyway-tests

[Sfurti-yb]

For the pg_advisory_lock is there a reason flyway takes out advisory locks and would disabling it have any negative impacts?

[Sfurti-yb]

Hi @Barry-RG, I have modified the code as per the review. Also the test repository is public now.

[ashetkar]

Thanks @Barry-RG! Is it possible to backport this fix to earlier versions so that it is available with latest Flyway 8.x or Flyway 9.x?

[Barry-RG]

@ashetkar unfortunately we do not support backwards compatibility. Flyway has typically been a supports latest project.

[ashetkar]

Thanks. What is the version of Flyway which includes this fix? I see this fix is included in the yugabytedb package with version 10.8.1 but not sure of the Flyway version it is included in.