fix: reorder migration 0011 operations to avoid username constraint conflict

Author: fullstackjam

migrations/0011_transfer_official_configs_to_real_user.sql

@@ -1,12 +1,12 @@
--- Step 1: Update real user's username to 'openboot'
-UPDATE users 
-SET username = 'openboot'
-WHERE id = 'google_102596069106824335469';
-
--- Step 2: Transfer all configs to real user
+-- Step 1: Transfer all configs to real user (while fake user still exists)
 UPDATE configs
 SET user_id = 'google_102596069106824335469'
 WHERE user_id = 'openboot-official';
 
--- Step 3: Delete the fake user
+-- Step 2: Delete the fake user (releases username constraint)
 DELETE FROM users WHERE id = 'openboot-official';
+
+-- Step 3: Update real user's username to 'openboot' (now safe - no conflict)
+UPDATE users 
+SET username = 'openboot'
+WHERE id = 'google_102596069106824335469';