[management] Clone test databases from a migrated template

Profiling the management unit suite per engine showed that nearly every
test in management/server spends 1.0 to 1.7 seconds creating its store
on MySQL and about 0.9 seconds on Postgres, against 0.3 seconds on
sqlite. The work is CREATE DATABASE followed by 26 pre-migrations, a
40-table AutoMigrate and 9 post-migrations, repeated for each of the
package's 133 store creation sites. That put the package at 10 minutes
of its 20 minute go test budget on a healthy runner, and over it on a
slow one.

Run the full migration once per process into a template database and
clone it for every test database. Postgres copies it server-side with
CREATE DATABASE ... TEMPLATE. MySQL has no equivalent, so the template's
SHOW CREATE TABLE statements are replayed into the new database with
foreign key checks off, which keeps the ON DELETE CASCADE constraints
that CREATE TABLE ... LIKE would drop. The per-test store then opens
with migrations skipped. Every test still gets its own database, so
isolation is unchanged.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EsVtbd7MxMVsS9vP1H6KPS

.github/workflows/tmp-management-timing.yml

@@ -64,7 +64,9 @@ jobs:
 
       - name: download mysql image
         if: matrix.store == 'mysql'
-        run: docker pull mlsmaycon/warmed-mysql:8
+        run: |
+          docker pull mlsmaycon/warmed-mysql:8
+          docker image inspect mlsmaycon/warmed-mysql:8 --format 'entrypoint={{json .Config.Entrypoint}} cmd={{json .Config.Cmd}} env={{json .Config.Env}}'
 
       - name: Build test summarizer
         run: go build -o /tmp/gotestsummary ./tools/gotestsummary