Permissions: Add Community Creator Role for `can_create`

[Samk13]

:heart: Thank you for your contribution!

Description

• The can_create permission will now have the option to check if RDM_COMMUNITY_REQUIRED_TO_PUBLISH is set to True, requiring the user to have the community manager role to create new communities.
• The community creator role name can be overridden from the user instance.
• Closes https://github.com/inveniosoftware/product-rdm/issues/183
• Update communities settings so it can always be closed if the config is True

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• [ ] I'm aware of the code of conduct.
• [ ] I've created logical separate commits and followed the commit message format.
• [ ] I've added relevant test cases.
• [ ] I've added relevant documentation.
• [ ] I've marked translation strings.
• [ ] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• [ ] I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Frontend

• [ ] I've followed the CSS/JS and React guidelines.
• [ ] I've followed the web accessibility guidelines.
• [ ] I've followed the user interface guidelines.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[ntarocco]

I think that this is not needed. You can override the community service permissions in your instance, as we did it in our instance at CERN, see example here.