Integrate JMTE hub to our existing infrastructure

[yuvipanda]

• Use 'jupyter-meets-the-earth' rather than jmte as name, because the existing cluster is already called 'jmte'.
• Replicates config from https://github.com/2i2c-org/infrastructure/pull/436/files
  to the extent possible
• Uses our IRSA config for AWS permissions, rather than the eksctl created service account in use earlier.
• Uses CILogon+GitHub for authentication, rather than auth0+github
• Re-use the same EFS filesystem from before, avoiding the need to copy a few terabytes of data around
• Hub is now at jmte.2i2c.cloud, and the old URL (hub.jupyterearth.org) redirects here. Same for staging.
• Existing sqlite db has been copied over to the new cluster, so all existing users have access. The JupyterHub
  admin panel was used to manage access, so the hub was the source of user lists
• No prometheus existed on old cluster, so no prometheus data needs to be copied over.
• The staging hub config matches the prod hub config to the extent possible, matching rest of our infrastructure.
• SFTP service has been removed for now.
• Fix typo in our domain redirects code that prevented more than one redirect from being set

Ref #2201

[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
gcp	leap	Yes	Support helm chart has been modified	No
kubeconfig	utoronto	Yes	Support helm chart has been modified	No
aws	ubc-eoas	Yes	Support helm chart has been modified	No
aws	nasa-cryo	Yes	Support helm chart has been modified	No
aws	openscapes	Yes	Support helm chart has been modified	No
gcp	linked-earth	Yes	Support helm chart has been modified	No
gcp	2i2c	Yes	Support helm chart has been modified	No
gcp	2i2c-uk	Yes	Support helm chart has been modified	No
gcp	pangeo-hubs	Yes	Support helm chart has been modified	No
aws	jupyter-meets-the-earth	Yes	Support helm chart has been modified	Yes	Following helm chart values files were modified: common.values.yaml, staging.values.yaml, enc-staging.secret.values.yaml
aws	victor	Yes	Support helm chart has been modified	No
aws	gridsst	Yes	Support helm chart has been modified	No
aws	nasa-veda	Yes	Support helm chart has been modified	No
gcp	qcl	Yes	Support helm chart has been modified	No
gcp	cloudbank	Yes	Support helm chart has been modified	No
gcp	awi-ciroh	Yes	Support helm chart has been modified	No
gcp	callysto	Yes	Support helm chart has been modified	No
aws	carbonplan	Yes	Support helm chart has been modified	No
gcp	meom-ige	Yes	Support helm chart has been modified	No
aws	2i2c-aws-us	Yes	Support helm chart has been modified	No
gcp	m2lines	Yes	Support helm chart has been modified	No

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, prod.values.yaml, enc-prod.secret.values.yaml

[yuvipanda]

I've deployed and set all this up already, as the existing cluster had gone down and I wanted to prevent disruptions.

[consideRatio]

Great work on this @yuvipanda!! LGTM!!!

[consideRatio]

Like for new hub setups, we want to provide permissions to work on this aws account for 2i2c engineers.

So, sending out invites is relevnt as well, but not directly related to this PR

[yuvipanda]

Thanks for the quick review and all the help, @consideRatio!

[github-actions]

🎉🎉🎉🎉

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