fix(issue-status): renumber migrations 200-206 -> 202-208 (MUL-4809)

main advanced past the earlier rebase and took 200/201 for the inbox
archived-listing indexes, so the PR's 200-206 collide once GitHub tests the
branch merged with main (TestMigrationNumericPrefixesStayUniqueAfterLegacySet
fails on the merge). Shift this slice's seven migrations to the next free
block, 202-208, and update the three in-file cross-references. SQL bodies are
unchanged; each concurrent index stays in its own single-statement file.

Co-authored-by: multica-agent <github@multica.ai>

server/migrations/202_issue_status.up.sql

@@ -11,7 +11,7 @@
 -- reference; tenant consistency and cleanup are enforced in app code (the
 -- workspace-delete path removes these rows in the same transaction). All
 -- indexes are created CONCURRENTLY in their own single-statement follow-up
--- migrations (201-204) because Postgres forbids CREATE INDEX CONCURRENTLY
+-- migrations (203-206) because Postgres forbids CREATE INDEX CONCURRENTLY
 -- inside this table-create transaction.
 CREATE TABLE issue_status (
     id UUID PRIMARY KEY DEFAULT gen_random_uuid(),

server/migrations/206_issue_status_workspace_id_index.up.sql

@@ -1,5 +1,5 @@
 -- Non-partial (workspace_id) index covering ALL rows, including archived ones.
--- The three catalog uniqueness indexes (201-203) are partial (active rows /
+-- The three catalog uniqueness indexes (203-205) are partial (active rows /
 -- non-NULL system_key), so none of them can serve the workspace-scoped
 -- delete/cleanup path that must remove every issue_status row for a workspace
 -- regardless of archived_at. Built CONCURRENTLY in its own single-statement

server/migrations/207_issue_status_id_column.up.sql

@@ -2,5 +2,5 @@
 -- window. No FK (CLAUDE.md); resolved to issue_status in app code. Nothing
 -- reads or writes it yet -- the legacy issue.status TEXT column stays the
 -- source of truth until the Phase 2 double-write lands. Its index is created
--- CONCURRENTLY in migration 206.
+-- CONCURRENTLY in migration 208.
 ALTER TABLE issue ADD COLUMN IF NOT EXISTS status_id UUID;