Allow upgrades on azure without Terraform changes on LBs created from within Kubernetes

[3u13r]

Context

Proposed change(s)

• Remove worker nodes from any existing load balancer backend, since any VM NIC can only be attached to one backend group. Also the worker backends were unused anyway.
• Let the cloud-controller-manager create a separate "kubernetes-lb" to create LBs for Kubernetes services.
• Don't inline (most) of the network security rules
  • Sadly, we cannot fix the upgrade process in one go, as we need 2 state changes on the same resource. So the upgrade to this release still removes the network security rules added by the cloud controller manager, but which should heal itself in the upgrade process one it's restarted. After we execute the instructions mentioned in the TODO, there will finally be no terraform changes after "constellation create" -> "create LB svc" -> "terraform plan".

Azure, snp, 1:2, lb: https://github.com/edgelesssys/constellation/actions/runs/11220341955
Azure, snp, 1:2, upgrade: https://github.com/edgelesssys/constellation/actions/runs/11220359763

Checklist

• Run the E2E tests that are relevant to this PR's changes
• Add labels (e.g., for changelog category)
• Is PR title adequate for changelog?
• Link to Milestone

[netlify]

✅ Deploy Preview for constellation-docs ready!

Name	Link
🔨 Latest commit	cf686d6
🔍 Latest deploy log	https://app.netlify.com/sites/constellation-docs/deploys/670646ae7541700008a40e23
😎 Deploy Preview	https://deploy-preview-3257--constellation-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Coverage report

Package	Old	New	Trend
internal/constellation/helm	34.50%	34.50%	🚧