Database Persistence Migration

We need to migrate the persistence layer of the Places backend into the new Well Known Components architecture.
Migrations already exist in the old project and must be reused to ensure full backward compatibility.
The goal is to copy the existing migrations, run them locally, and validate they work as expected.

- [ ] Configure migration tool in the new service (same as the old backend).
- [ ] Clone the Zone database locally to use as a starting point.
- [ ] Run `yarn migrate down 100` and verify no errors occur.
- [ ] Run `yarn migrate up` and confirm the database schema matches the original (without data).
- [ ] Re-clone the Zone database to restore test data for local development.
- [ ] Document the process (clone DB, migrate down, migrate up, re-clone DB) in the README.

Start by comparing the new service with the old backend to identify the existing migrations and migration-tool configuration. Clone the Zone database locally, run `yarn migrate down 100` and `yarn migrate up`, and compare the resulting schema with the original without data. Restore the test data by re-cloning the database and document the full process in the README.

Written by the indexing model from the issue text.