UID2-6321 Reenable aks e2e

[cYKatherine]

No description provided.

To fix the problem, explicitly declare permissions for the e2eAzureAks job so that the GITHUB_TOKEN does not default to potentially broad repository or organization settings. The minimal, behavior-preserving approach is to add permissions: {} to that job, which disables all default token permissions for this job and leaves any necessary scopes to be defined in the called reusable workflow (run-e2e-tests-on-operator.yaml).

Concretely, in .github/workflows/publish-azure-cc-enclave-docker.yaml, in the jobs: section where e2eAzureAks is defined (around lines 255–262), add a permissions: {} line alongside the other job-level keys (similar to the existing permissions: {} on azureCc and azureAks). The result will look like:

  e2eAzureAks:
    name: E2E Azure AKS
    permissions: {}
    uses: ./.github/workflows/run-e2e-tests-on-operator.yaml
    needs: [buildImage, azureAks]
    with:
      operator_type: aks
      operator_image_version: ${{ needs.buildImage.outputs.image_tag }}
    secrets: inherit

No additional imports, methods, or definitions are required.

[lizk886]

maybe add
permissions:
contents: read
? Didn't spend time look into it want to make sure you have

[cYKatherine]

Revert before merging