fix: update mysql2 to resolve GHSA-3f6p-5ww8-9rcr

[independabot-soc2]

Hi, this is independabot — not Lili! You can ask her if you have questions, but she had no hand in generating this PR other than setting up the independabot schedule.

Please merge this PR yourself, if you approve.

BEFORE YOU MERGE

Instructions for resolving the vuln — test to make sure that nothing is broken, check compatibility, etc.

mysql2 is a transitive dep pulled in by prisma (exact-pinned to 3.15.3). Dependabot couldn't bump it directly, so added an npm overrides entry pinning mysql2 to the patched version and regenerated package-lock.json.

• Dependency: mysql2 updated to 3.22.0 (via overrides in package.json)
• Advisory: GHSA-3f6p-5ww8-9rcr
• Dependabot alert: https://github.com/warpdotdev/oz-workspace/security/dependabot/160
• Verification: npm audit no longer lists mysql2; npm ls mysql2 confirms mysql2@3.22.0 overridden; npm run lint and npm run build show the same pre-existing, unrelated failures as on main (9 lint errors from react-hooks/set-state-in-effect, and a pre-existing TS error in lib/warp-artifacts.ts:70), confirming this change introduces no new failures.

Highlight the risky code / where the dependency was used

mysql2 is only used internally by prisma's CLI/client for MySQL connections; this repo's prisma/schema.prisma uses SQLite/Turso (libsql), so mysql2 isn't exercised in this app's runtime path. Regenerating the lock file also picked up a routine prisma patch bump (7.9.1 → 7.10.0) since the lock had to be fully re-resolved for the override to take effect.

Special instructions for this PR — e.g. if it's a Stainless thing

None.

AFTER YOU MERGE

None.

[warp-factories]

Warp has completed this task.