[openscapes] Offer just one allocation option for the workshop on a bigger machine:

[GeorgianaElena]

Fixes #6370

Changes

• This PR uses Improve resource allocation choice generator #6313 to re-generates 5 choices on a r5.4xlarge.
• The option that was closest to the community's 14.8 GB RAM / up to 3.7 CPU is chosen, i.e. ~15 GB RAM, ~1.9 CPUs, up to 15 cpu
• It removes all other resource options that are not used and all other image options that are not used in the workshop

It's important to note that this choice is now on a r5.4xlarge instead of a r5.xlarge, which means that it will pack 8 users on a node instead of two, allowing for smaller startup time.
At ~200 users, there will be around 25 scale up events on a r5.4xlarge, whereas on a r5.xlarge there would have been 100 events.

*This change should be reverted after the workshop

[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	openscapes	staging	Following prod hubs require redeploy: workshop

Production deployments

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

[GeorgianaElena]

This is how it looks like deployed. @jnywong, what do you think?

[jnywong]

This is great! The instructor will do a test run tomorrow, so hopefully we know about any potential issues ahead of time.

I've added a follow up issue to revert these changes #6382

Thank you Georgiana :)

[github-actions]

🎉🎉🎉🎉

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