AWS cost attribution: split dask workers of each hub in all clusters into their own nodegroups

[GeorgianaElena]

For each cluster in the list below, perform the following actions:

- [x] Create the same set of dask worker nodes for each hub in a cluster
- [x] Configure each of the hubs so their dask workers only spawn on the nodepools designated for them
- [x] Tag each of the nodepool with `2i2c:hub-name` to match the name of the hub
- [x] Tag each of the dask nodepools with `2i2c:node-purpose` set to `worker`

• [x] 2i2c-aws-us https://github.com/2i2c-org/infrastructure/pull/5106
• [x] catalystproject-africa
• [x] gridsst
• [x] jupyter-health
• [x] kitware
• [x] nasa-cryo
• [x] opensci
• [x] smithsonian
• [x] strudel
• [x] ubc-eoas
• [x] victor
• [x] nmfs-openscapes
• [x] openscapes
• [x] earthscope
• [x] jupyter-meets-the-earth
• [x] nasa-ghg
• [x] nasa-veda
• [x] projectpythia (they are using other cost allocation system https://github.com/2i2c-org/meta/issues/1612)

Reference

See https://github.com/2i2c-org/infrastructure/issues/4485

• [ ] Users across these hubs will spawn dask workers on to their own nodepools, and not share them with users on other hubs.
• [ ] There is a tag 2i2c:hub-name, 2i2c:node-purpose on nodes spawned by dask-gateway. You can verify this by looking at EC2 instances on the AWS console.
• [ ] the cost of each hub shows up in its respective grafana