Research on Yoyo DB Migrations

[kylecdrck]

Problem/Motivation
Currently, our DB migration executes whenever our application is deployed and run. With this, we lack the flexibility to run only db migrations separately without triggering a service deployment.

In addition, we cannot also roll back DB changes, just in case we encounter some issues related to DB migrations.

Proposed Solution
Research more on Yoyo Migrations about the following

• Separately running it as a job without the need for a redeployment (similar to executing maven commands for Liquibase)
• Having a rollback procedure on existing migrations

All findings should be documented in our Wiki. No code or infra changes should be done yet