fix(mariadb): emit NOCYCLE/NOCACHE on ALTER SEQUENCE

[huyplb]

Summary

The web E2E suite surfaced a MariaDB migration failure. When a sequence differs between source and target, the generator's ALTER SEQUENCE path built its statement directly and — unlike the CREATE SEQUENCE path — never routed through MariaDB's wrapCreateSequence normalizer. So it emitted:

ALTER SEQUENCE order_seq RESTART WITH 1000 INCREMENT BY 1 MINVALUE 1 MAXVALUE 9223372036854775806 NO CYCLE CACHE 1000;

MariaDB requires the single tokens NOCYCLE/NOCACHE and rejects the spaced form:

You have an error in your SQL syntax ... near 'CYCLE CACHE 1000'

That aborted and rolled back the entire migration (2 MariaDB E2E assertions failed).

Fix

• New wrapAlterSequence(qualifiedName, alterSql) dialect hook, mirroring the existing wrapCreateSequence. Default is a no-op — Postgres/DB2/SQL Server/Oracle are unaffected (they accept NO CYCLE/NO CACHE).
• The MariaDB dialect implements it, and the NO CYCLE→NOCYCLE / NO CACHE→NOCACHE normalization is factored into a shared normalizeSequenceTokens helper used by both the CREATE and ALTER paths, so they can't drift again.

Test plan

• New unit test asserts the MariaDB ALTER emits NOCYCLE/NOCACHE and never NO CYCLE/NO CACHE
• npx vitest run — 242 passed, 2 skipped
• cd apps/web && npx tsc --noEmit — clean
• Verified against the real MariaDB container: the old SQL errors, the new SQL succeeds (exit 0)
• Web E2E: MariaDB went from FAIL to 10/10; full clean re-run of all 6 configured dialects (PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, DB2) is 6 passed / 0 failed

🤖 Generated with Claude Code