e2e: add mssql container to scaffold.runtime boot matrix (follow-up to #208)

[rickylabs]

Summary

The scaffold.runtime E2E suite (packages/cli/e2e) now boots three engines end-to-end — postgres, mysql, sqlite — as of the CRUD-surface CODE PR (#208). The fourth product engine, mssql (sqlserver provider), is currently proven in #208 by a typecheck-proof only: scaffold --service --db mssql → db generate → deno check of the generated workspace (all green). It does not yet get a real e2e-boot in the matrix.

This is by owner decision (the "3 boot + mssql typecheck" bar for #208, to keep that PR's gate tractable). This issue tracks closing the gap.

Task

Add mssql to the real scaffold.runtime e2e-boot matrix so all four product engines boot end-to-end:

• Add MSSQL: 'mssql' to the DATABASE axis in packages/cli/e2e/src/domain/extension-axes.ts.
• Accept mssql in packages/cli/e2e/src/presentation/cli/options/run-options.ts (parseDatabase + error message).
• Wire the mssql container into the e2e Aspire/database boot path (application/gates/scaffold + database-gates.ts): SQL Server image (e.g. mcr.microsoft.com/mssql/server), ACCEPT_EULA, SA_PASSWORD/strong-password policy, health-wait, and the sqlserver connection-string shape.
• Prove deno task e2e:cli run scaffold.runtime --db mssql --cleanup --format pretty green (scaffold → plugins → db init/generate/seed → registry → typecheck → Aspire restore/start → runtime/endpoint/plugin/auth/OTEL → cleanup).

Notes

• mssql requires a container (unlike sqlite); the sqlite container-less handling landed in feat(cli): scaffold CRUD surface DX upgrade (C1–C10) [#153 CODE] #208 as a reference for the axis plumbing.
• SQL Server on Linux containers has a longer cold-start than postgres/mysql — budget the health-wait accordingly.
• Blocked-by / follow-up to feat(cli): scaffold CRUD surface DX upgrade (C1–C10) [#153 CODE] #208.