feat(migration-service): initialize database schema management

[mijinummi]

Description

This PR addresses issue #362 by creating the dedicated migration-service infrastructure layer. This service isolates heavy structural modifications, handles data validation checkpoints, processes dynamic rollback blocks natively via execution wrappers, and establishes a blueprint for safe expand-and-contract column handling.

Changes Introduced

• Atomic Operations Context: Encapsulated migration scripts within explicit database transaction blocks (queryRunner) to guarantee atomicity.
• State Control Matrix: Built the global_migration_records schema to keep cluster instances aligned on applied versions.
• Fail-Safe Rollback Engine: Stored structural down-scripts directly in historical entries to ensure precise schema restoration during system failures.

Acceptance Criteria Verified

• Application service context provisions, connects, and tests dependencies cleanly in full isolation.
• Failed DDL/DML update invocations fully revert intermediate adjustments without breaking table integrity.
• Up-to-date tracking queries return structural layout histories sequentially.

Closes #362

[drips-wave]

@mijinummi Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits