Server project permissions are a bit weird

[penguinencounter]

Please confirm the following.

• I checked the existing issues for duplicate feature requests
• I have checked that this feature request is not on our roadmap

What parts of Modrinth is your feature request related too?

Modrinth.com website

Is your suggested feature related to a problem? Please describe.

This is the current state of server project permissions (after #5525 and #5526):

This leads to the following behavior:

• yes edit details + yes update content = can change compatibility to anything, including Custom Modpack
• yes edit details + no update content = can change compatibility to Vanilla or Published Modpack but not Custom Modpack
• no edit details + yes update content = can't change compatibility at all

Describe the solution you'd like

A way to give someone permission to update the compatibility settings (say, updating a custom or published modpack), without being able to change the server's name, address, summary, etc.

(Ideally, the Update content permission would do this, and Edit details wouldn't give permission to change the compatibility settings.)

Describe alternatives you've considered

alternative: it could potentially be left as is, because being able to change the modpack is roughly the same amount of risk as updating any of the other fields in the Edit details permission?

• it may make sense to consolidate the two permissions in this case
• custom modpacks are just versions under the hood (and Update content is just Upload version with a different name) so that might be a bit awkward

Additional context

thanks for the quick patch :)