chore(db): keep the 0262_strong_storm migration bookkeeping

The message_id migration already ran against the DB in every env, so the
column exists everywhere regardless of this revert. Restore the migration
file, its snapshot, the journal entry, and the schema.ts column declaration
so the tree matches the DB and the recorded migration history; the revert
keeps out only the v0.8 code. packages/db is now byte-identical to staging.

Author: Sg312

packages/db/migrations/0262_strong_storm.sql

@@ -0,0 +1 @@
+ALTER TABLE "workspace_files" ADD COLUMN "message_id" text;