fix(agent-evolution-pool-supervisor): Fix earliest milestone test data so v3.2.0 has earliest due date

The step_repo_has_multiple_milestones step previously added v3.1.0 with the earliest due_on date, causing the 'earliest open milestone' lookup to return v3.1.0 instead of the expected v3.2.0. Replaced v3.1.0 with v3.4.0 and gave v3.2.0 the earliest due date to match the feature-file expectation.

ISSUES CLOSED: #7888

features/steps/agent_evolution_pool_supervisor_metadata_steps.py

@@ -83,22 +83,22 @@ def step_label_name_is(context: Any, label_name: str) -> None:
 @given("the repository has multiple open milestones")
 def step_repo_has_multiple_milestones(context: Any) -> None:
     """Add multiple open milestones to the repository."""
-    context.milestones["v3.1.0"] = {
-        "id": 41,
-        "state": "open",
-        "name": "v3.1.0",
-        "due_on": "2026-01-31T23:59:59Z",
-    }
     context.milestones["v3.2.0"] = {
         "id": 42,
         "state": "open",
         "name": "v3.2.0",
-        "due_on": "2026-02-26T23:59:59Z",
+        "due_on": "2026-01-31T23:59:59Z",
     }
     context.milestones["v3.3.0"] = {
         "id": 43,
         "state": "open",
         "name": "v3.3.0",
+        "due_on": "2026-02-28T23:59:59Z",
+    }
+    context.milestones["v3.4.0"] = {
+        "id": 44,
+        "state": "open",
+        "name": "v3.4.0",
         "due_on": "2026-03-31T23:59:59Z",
     }