Register exec env tables in storage migration

Why: Schema 35 adds exec_env_requests and exec_env_bindings. The SQLite-to-Postgres copier refuses to run when a business table is missing from its ordered list.
Evidence: SELF go test ./cmd/storage-migrate -run TestCopyOrderCoversAllFixtureTables. CI run 3343 failed on this exact check.
Impact: Those two tables move with the rest of the database. They have no foreign keys, so they can follow the existing recovery tables.
Refs: pull 206
Co-authored-by: Cursor <cursoragent@cursor.com>

cmd/storage-migrate/main.go

@@ -298,6 +298,8 @@ var copyOrder = []string{
 	"account_events",
 	"redeem_attempts",
 	"recovery_proposals", "recovery_proposal_proofs",
+	// v35 分层 Python 环境（无外键；申请与会话绑定要随库迁走）
+	"exec_env_requests", "exec_env_bindings",
 }
 
 const controlDDL = `