Give the next-only mixed-profile suite a suite array

The parity guard now checks that every suite the local runner can dispatch has a backing suite array, so a suite dispatched without one is visible to nobody. On next, mixed-profile was dispatched by a bare call with no array, so the guard reported it as present on the GitHub matrix and missing from the local runner even though the local runner does run it.

This adds MIXED_PROFILE_SUITES, dispatches through it in the same idiom the admission-cap suite uses so the array is the single source of truth for whether the suite runs, and lists it in the suite listing. It exists only on next, so it is authored here directly rather than merged up.

testing/ci-local.sh

@@ -93,6 +93,7 @@ ONLY_SUITE=""
 # All integration suites matching ci.yml
 STATIC_SUITES=(static-mesh static-chain)
 REKEY_SUITES=(rekey rekey-accept-off rekey-outbound-only)
+MIXED_PROFILE_SUITES=(mixed-profile)
 ADMISSION_SUITES=(admission-cap)
 # Each entry: "display-name scenario [--flag value ...]"
 CHAOS_SUITES=(
@@ -148,6 +149,9 @@ list_suites() {
     echo "  Rekey:"
     for s in "${REKEY_SUITES[@]}"; do echo "    $s"; done
     echo ""
+    echo "  Mixed profile:"
+    for s in "${MIXED_PROFILE_SUITES[@]}"; do echo "    $s"; done
+    echo ""
     echo "  Admission cap:"
     for s in "${ADMISSION_SUITES[@]}"; do echo "    $s"; done
     echo ""
@@ -859,7 +863,9 @@ run_integration() {
     run_rekey_outbound_only
 
     # Mixed-profile (Full + NonRouting + Leaf)
-    run_mixed_profile
+    for _suite in "${MIXED_PROFILE_SUITES[@]}"; do
+        run_mixed_profile
+    done
 
     # Admission cap (mesh profile, max_peers=1 on one node)
     for _suite in "${ADMISSION_SUITES[@]}"; do