Fix Mixed Case AutoIncrement Leaving Stale SQLite Sequence ROws

[redixhumayun]

Description

This PR changes the instructions emitted during DROP TABLE to emit the normalized table name for accurate comparison.

Motivation and context

This PR closes #5807

The issue was that during instruction emission, the non-normalized table name was being used, whereas what is stored is the normalized table name for SQLite sequence.

Description of AI Usage

This PR was written entirely by AI agents (Codex) with Claude reviewing the output. It took a little back and forth to force the agent to scope the changes tightly. For instance, Claude doesn't seem to understand that storing the lowercase name is an explicit design choice in Turso because SQLite does the opposite.

Reproduction Of Fixed Sequence

turso> CREATE TABLE "MiXeD Name"(id INTEGER PRIMARY KEY AUTOINCREMENT, v);
turso> INSERT INTO "MiXeD Name"(v) VALUES('x');
turso> DROP TABLE "MiXeD Name";
turso> CREATE TABLE "MiXeD Name"(id INTEGER PRIMARY KEY AUTOINCREMENT, v);
turso> INSERT INTO "MiXeD Name"(v) VALUES('y');
turso> SELECT id,v FROM "MiXeD Name";
┌────┬───┐
│ id │ v │
├────┼───┤
│  1 │ y │
└────┴───┘
turso> SELECT name,seq FROM sqlite_sequence;
┌────────────┬─────┐
│ name       │ seq │
├────────────┼─────┤
│ mixed name │   1 │
└────────────┴─────┘

[turso-bot]

Please review @penberg

[PThorpe92]

lgtm 👍