Implement database migrations

[ben-ryder]

Work in progress on main branch, see b1cb335

Regressions to fix:

• Missing unique constriant on user email
• Missing automatic updating of updatedAt timestamps for users/vaults
• E2E test failure in API response to /v1/auth/login [POST]
• Unique constriant of vault name for a given user is missing
• Unique constriant on vault id (primary key) returning 500 errors not 400

Other issues

• imporve docs/further test required database permissions.
• migrate needs permission to create schema, which may not be possible on hosted platforms (see [PG] Allow migration without CREATE SCHEMA permission drizzle-team/drizzle-orm#4025)
• migrations output noise in logs

[ben-ryder]

Implementation now passes tests and works locally when running in dev mode and prod build.
Still needs further testing around running on hosted envs before closing, as there may be issues.

Migrations have also been edited manually to rename the files and ensure constraints and triggers are correctly included, this it worth keeping an eye on going forward as it may be worth reevaluating migration tools if that much manual work is required anyway (for example using https://github.com/porsager/postgres-shift or more widly used tool instead).