Cleanup redudant cluster config that was re-setting default values

[consideRatio]

• refactor: cleanup redundant config about dask-gateway idle_timeout
• refactor: cleanup redundant config about matchNodePurpose

[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	jupyter-meets-the-earth	No		Yes	Following helm chart values files were modified: common.values.yaml
aws	carbonplan	No		Yes	Following helm chart values files were modified: common.values.yaml
aws	openscapes	No		Yes	Following helm chart values files were modified: common.values.yaml
gcp	meom-ige	No		Yes	Following helm chart values files were modified: common.values.yaml

Production deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
aws	jupyter-meets-the-earth	prod	Following helm chart values files were modified: common.values.yaml
aws	carbonplan	prod	Following helm chart values files were modified: common.values.yaml
aws	openscapes	prod	Following helm chart values files were modified: common.values.yaml
gcp	meom-ige	prod	Following helm chart values files were modified: common.values.yaml

[yuvipanda]

I'm assuming idle_timeout is now specified upstream? If so, good to go

[consideRatio]

I'm assuming idle_timeout is now specified upstream? If so, good to go

Yepp in our own daskhub helm chart's default values - see

infrastructure/helm-charts/daskhub/values.yaml

Lines 212 to 214 in 6223891

	idle: |
	# timeout after 30 minutes of inactivity
	c.KubeClusterConfig.idle_timeout = 1800

[github-actions]

🎉🎉🎉🎉

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