Fixing issue of app not throwing an error when Flyway migration fails

[jonathanlbt1]

Problem

This pull request includes changes to improve error handling and code readability in the MarquezApp class. The most important changes include adding a custom exception, modifying the run method to throw the new exception, and improving code formatting whenever Flyway fails a migration.

Closes: #3033

Solution

• api/src/main/java/marquez/MarquezApp.java: Added the DbException import and modified the run method to throw DbException on database migration errors instead of logging and terminating the application. [1] [2] [3]

Note: All database schema changes require discussion. Please link the issue for context.

One-line summary:

Checklist

• You've signed-off your work
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• You've included a one-line summary of your change for the CHANGELOG.md (Depending on the change, this may not be necessary).
• You've versioned your .sql database schema migration according to Flyway's naming convention (if relevant)
• You've included a header in any source code files (if relevant)

[boring-cyborg]

Thanks for opening your first pull request in the Marquez project! Please check out our contributing guidelines (https://github.com/MarquezProject/marquez/blob/main/CONTRIBUTING.md).

[netlify]

❌ Deploy Preview for peppy-sprite-186812 failed.

Name	Link
🔨 Latest commit	2358703
🔍 Latest deploy log	https://app.netlify.com/sites/peppy-sprite-186812/deploys/67ce2502fff3f9000958a38b