Add defined-term-access-2i2c to allowed organizations

[ateucher]

This team is a parent team in NASA-Openscapes, where subteams will be created to allow access to the hub for a defined term. I'm hoping this workflow will allow us to manage short-medium term team-level access by creating new teams under defined-term-access-2i2c and removing them from the parent team when their access period is over, and not having to do PR's on this config every time.

[github-actions]

Merging this PR will trigger the following deployment actions.

Support deployments

No support upgrades will be triggered

Staging deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
aws	openscapeshub	staging	Following helm chart values files were modified: common.values.yaml

Production deployments

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

[github-actions]

🎉🎉🎉🎉

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