[victor] Upgrade k8s version, separate nodepools per hub, enable cost-allocation

[GeorgianaElena]

Ref #4878

[github-actions]

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider	Cluster Name	Upgrade Support?	Reason for Support Redeploy	Upgrade Staging?	Reason for Staging Redeploy
aws	victor	Yes	Following helm chart values files were modified: support.values.yaml	Yes	Following helm chart values files were modified: staging.values.yaml

Production deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
aws	victor	prod	Following helm chart values files were modified: prod.values.yaml

[consideRatio]

Great @GeorgianaElena!

It isn't obvious if 2i2c ought to split apart node pools and home directory storage infra to become hub specific. I made a call with some discussion in #4928 that we should not do so without explicit opt-in.

The documentation you followed was written before the decision was made about this, so its written uncertain about this and hasn't been updated to reflect something about it yet.

I figure its not a problem for victor to have a split node pool for staging/prod, but for the clusters going onwards I figure we should go with the minimalistic act of using shared node pools and shared EFS storage unless they already have a separation there.

[github-actions]

🎉🎉🎉🎉

Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/11628774804