Database Migrations done right

[milosmns]

Provide a brief summary of the planned work

All previous database migrations have been run manually or through a simple sequencer in-code. This should not happen because the project is now stable enough and would benefit from a professional database schema management tool.

Detailed overview

Some popular schema management tools are:

• Liquibase
• Flyway

In addition to the schema management tool, it looks like we can completely replace Spring Boot's JPA tooling for schema management. One open question is: will it work with the in-memory H2 database?

Hint/location:

com.appifyhub.monolith.features.init.domain.SchemaInitializer

List the acceptance criteria

• Manual database schema management is no more (use current db as base)
• Unnecessary tooling such as JPA is removed from code and dependencies [if possible]
• Tests are updated to reflect these changes, and passing

Include any additional notes (optional)

No response

[milosmns]

Related issues:

• https://github.com/appifyhub/monolith/issues/179
• https://github.com/appifyhub/monolith/issues/180