Let node resource-allocation script handle optimizations for events

[consideRatio]

The script developed in #3030 provides resource allocation choices, but the choices are opinionated to reduce cloud costs rather than startup speeds etc.

For example, if the user can choose from ~1GB to ~128GB resource allocation, the user will for requests up to ~32 GB be scheduled on 32 GB node and for requests above that be put on a 128 GB node. A community hosting an event that will have users start with ~16GB resource allocation requests should probably instead be scheduled on 128GB nodes (or even 512GB nodes), as then at least 8 (32) users can fit on the node, instead of just 2 on the smaller 32 GB node.

I'd like this issue to represent the development of a functionality allowing us to specify something when using the script in #3030, so that we can make it generate choices suitable for an event. A preliminary idea on how to specify this could be by specifying the minimum amount of users per node to fit before opting to use a larger node. For events, we could then specify we want at least 8 users per node, and have the ~16GB requests fit be made to schedule on the ~128 node instead of the ~32GB node given ~32 / ~128 / ~512 GB nodes are the available node types.