feat: Run the full E2E suite set automatically on release PRs

[njuettner]

Towards giantswarm/roadmap#4334

Release PRs are created with an empty body, so Tekton — which starts the tests from a /run line in the PR body — never ran anything on them. Running the E2E tests depended on someone remembering to comment, and release PRs were merged with no run at all (cluster-aws#2036, cluster-cloud-director#573, cluster-vsphere#527).

Adds .github/release-pr-body.md, which giantswarm/github-workflows#266 uses as the release PR body. cluster-test-suites already expands to every suite for this provider once it detects a release PR, so no suite parameters are needed here.

Has no effect until giantswarm/github-workflows#266 merges; until then the file is simply unused.

[github-actions]

There were no differences in the rendered Helm template.

Output

=== Differences when rendered with values file helm/cluster-aws/ci/test-auditd-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-default-node-pools-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-eni-mode-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-hop-count-tuning-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-irsa-crossplane-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-karpenter-arm64-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-karpenter-full-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-karpenter-mixed-with-regular-nodepools-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-karpenter-system-reserved-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-karpenter-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-lifecycle-hook-heartbeattimeout-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-local-registry-cache-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-machinehealthcheck-node-problem-detector-used-control-plane-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-machinehealthcheck-node-problem-detector-used-workers-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-machinepool-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-mc-proxy-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-multiple-authenticated-mirrors-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-multiple-service-account-issuers-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-multiple-vpc-cidrs-eni-mode-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-multiple-vpc-cidrs-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-network-topology-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-nodeport-cidrs-eni-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-nodeport-cidrs-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-non-default-vpc-cidr-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-spot-instances-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-subnet-tags-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-vpc-id-values.yaml ===

No difference


=== Differences when rendered with values file helm/cluster-aws/ci/test-wc-minimal-values.yaml ===

No difference


=== No differences at all ===

[njuettner]

/skip-ci This change does not affect what's being tested by CI.

[tinkerers-ci]

🚨 CI checks were skipped

Skip reason: This change does not affect what's being tested by CI.
Skipped by: @njuettner