Update hubs to use new resource allocations

[yuvipanda]

#7271 was a result of Brian reporting that the 29.7GB option wasn't working on the disasters hub. We knew this was an issue, and updated our resource allocation script to handle this well in #6313. But that wasn't rolled out to all hubs, as that's a user facing change.

Now that it's affecting users, let's roll it out to all hubs.

This involves some copy pasting to make sure 'allowed groups' config sticks.

Definition of done

New resource allocation changes are rolled out to the following hubs

• 2i2c-jetstream2
• maap — [maap, *] Update profile list resource constraints #7431
• nasa-ghg-hub — [nasa-ghg-hub, *] Update profile list resource constraints #7430
• nasa-veda — [nmfs-openscapes, *] Update profile list resource constraints #7402
• nmfs-openscapes ­— [nmfs-openscapes, *] Update profile list resource constraints #7402
• opensci — [opensci, *] Update profile list resource constraints #7403
• reflective
• smithsonian — [smithsonian, *] Update profile list resource constraints #7401
• victor — [victor, *] Update profile list resource constraints #7400

[yuvipanda]

Someone ran into this on VEDA today