gha: capture feature status per cluster in the MCS API conformance test

The MCS API conformance job runs two clusters but never produced a
features-tested artifact, so the upload and the run-level merge warned about
the missing artifact on every run. A single features status on the default
context would only cover one of the two clusters.

Add explicit per-cluster feature-status steps, one per context, mirroring the
conformance-clustermesh job. post-logic keeps capture_features_tested false,
as the features are now collected by these dedicated steps.

This commit was prepared with AIL:3.

Signed-off-by: André Martins <andre@cilium.io>

Author: aanm

.github/workflows/conformance-mcs-api.yaml

@@ -343,6 +343,20 @@ jobs:
           retention-days: 5
           if-no-files-found: ignore
 
+      - name: Features tested on cluster 1
+        uses: ./.github/actions/feature-status
+        with:
+          cilium-cli: "cilium --context ${{ env.contextName1 }}"
+          title: "Summary of all features tested on cluster 1"
+          json-filename: "${{ env.job_name }} (${{ join(matrix.*, ', ') }}) - cluster 1"
+
+      - name: Features tested on cluster 2
+        uses: ./.github/actions/feature-status
+        with:
+          cilium-cli: "cilium --context ${{ env.contextName2 }}"
+          title: "Summary of all features tested on cluster 2"
+          json-filename: "${{ env.job_name }} (${{ join(matrix.*, ', ') }}) - cluster 2"
+
       - name: Run common post steps
         if: ${{ always() && steps.install-cilium.outcome != 'skipped' }}
         uses: ./.github/actions/post-logic