chore(db): regenerate the sync lock token migration as 0298

#6921 merged first and took 0297 for an unrelated column on a different table,
so this branch's migration is regenerated rather than renamed. Renaming would
leave the snapshot describing the wrong ordinal, and drizzle diffs against that
snapshot to decide what the next migration contains.

The regenerated statement is the lock token column alone — it correctly diffs
against staging's 0297 snapshot rather than re-emitting the column that landed
there.

Author: waleedlatif1

packages/db/migrations/0298_nasty_madrox.sql

@@ -0,0 +1 @@
+ALTER TABLE "knowledge_connector" ADD COLUMN "sync_lock_token" text;