ci: parallelize upgrade e2e test

[msanft]

Context

While working a lot with the e2e test, it became apparent that the curent start-to-feedback time is quite slow. Therefore, the test could be sped up a little.

Proposed change(s)

• Parallelize building the upgrade target CLI and spinning up the upgrade origin cluster to be concurrent, and then perform the actual e2e test afterwards.

Additional info

• AB#3619
• Upgrade E2E Test

Checklist

• Add labels (e.g., for changelog category)
• Is PR title adequate for changelog?
• Link to Milestone

[netlify]

✅ Deploy Preview for constellation-docs canceled.

Name	Link
🔨 Latest commit	9724111
🔍 Latest deploy log	https://app.netlify.com/sites/constellation-docs/deploys/65aa3155d7d8e60008500964

[daniel-weisse]

We need to upload the working dir from the create-cluster job, and download it in the e2e-upgrade job, otherwise we are missing some files to run the upgrade.

We should also either add a terminate-on-failure step to the create-cluster job in case anything goes wrong in that job, or split the terminate step into its own job, which runs if either create-cluster, or e2e-upgrade fails.
If ran as its own job, the terminate action requires access to the working directory, which means we would need to unconditionally upload the working dir from create-cluster, even if a step fails.

[msanft]

Another E2E Test: https://github.com/edgelesssys/constellation/actions/runs/7273685348

[daniel-weisse]

Should merge after #2567

[msanft]

Blocked until we can encrypt multiple-file artifacts

[msanft]

Upgrade tests suceeded for all clouds:

• https://github.com/edgelesssys/constellation/actions/runs/7581234827
• https://github.com/edgelesssys/constellation/actions/runs/7581236626
• https://github.com/edgelesssys/constellation/actions/runs/7581238230