generate flyway migrations from hibernate update scripts

[rmanibus]

fix #43723

Current Process: When creating a database migration, the workflow is quite cumbersome:

• Modify the entity.
• Check the update script in the dev UI (when accessible—sometimes the app doesn't even start, making it unavailable).
• Manually create a new migration file.
• Customize the update script as needed.

This process involves redundancy, as the entity already contains the necessary information to at least generate a draft migration.

New Workflow: With this pull request, the process is simplified to:

• Modify the entity.
• Customize the update script as needed.

Migration naming convention:

• major version is extracted from the previous migration
• minor version is the current timestamp (current format is yyyyMMddHHmmss, but I think flyway might support something more readable like yyyy_MM_dd_HH_mm_ss)

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

[quarkus-bot]

/cc @gsmet (hibernate-orm), @yrodiere (hibernate-orm)

[rmanibus]

how can I actually check the content if the generated file here ?

[gsmet]

@phillip-kruger I think we need your help here :)

[gsmet]

Thanks for the contribution. Could you clarify how it works and the cases that are covered?

[rmanibus]

Thanks for the contribution. Could you clarify how it works and the cases that are covered?

@gsmet just updated the PR description