allowClientClassCreation Based on Roles

New Feature / Enhancement Checklist

• [ x] I am not disclosing a vulnerability.
• [ x] I am not just asking a question.
• [ x] I have searched through existing issues.

Current Limitation

allowClientClassCreation Is limited to true or false no ability to condition. I'd like to be able to set an array of Role names, this will allow class creation permission to be granted to a subset of users/roles.

Feature / Enhancement Description

allowClientClassCreation Should accept an array of role names or something more complex permission structure, I can see that there are a few places that need an extra array includes check. and maybe user role fetching.

Example Use Case

If this is available we will be able to build functionality while the app remains active.
It is useful if your using parse as a app platform running smaller interconnected apps. You have a developer User that can add functionality without the need to restart the server. Might be niche, thoughts?

Alternatives / Workarounds

None

3rd Party References

Not that I know of

Start by tracing the allowClientClassCreation configuration and the existing class-creation permission checks, then examine how user roles are fetched. Define the supported role-name configuration and verify that only users in those roles can create classes while existing boolean behavior remains intact.