Merged PR 2920: Adapt user migration configuration to take into account V2 migrated users

# Description

Prepares setup to automatically detect V2 migrated users from old dash to new dash by using the new claim type KygMoveDate.

# Checklist

- [X] The edited models and dependants run properly with production data. **Works well with current setup but there's no migrated users yet. We'll need to double check once the launch date has happened**
- [ ] The edited models are sufficiently documented. **N/A**
- [ ] The edited models contain PK tests, and I've ran and passed them. **N/A**
- [ ] I have checked for DRY opportunities with other models and docs. **N/A**
- [ ] I've picked the right materialization for the affected models. **N/A**

# Other

- [ ] Check if a full-refresh is required after this PR is merged.

Related work items: #20810

macros/user_migration_configuration.sql

@@ -30,12 +30,18 @@ Important note: if a user migrates once a phase has started, we
             "phase_name": "MVP",
             "claim_type": "KYGMVP",
             "default_deployment_date": "2024-07-30",
-            "claim_enforcement_priority": 1,
+            "claim_enforcement_priority": 2,
         },
         {
             "phase_name": "MVP",
             "claim_type": "MVPMIGRATEDUSER",
             "default_deployment_date": "2024-09-10",
+            "claim_enforcement_priority": 1,
+        },
+        {
+            "phase_name": "V2",
+            "claim_type": "KYGMOVEDATE",
+            "default_deployment_date": "2024-10-08",
             "claim_enforcement_priority": 0,
         },
     ] %}