Make communities required for submissions

[cc-a]

• Issue: Investigate backport of v13 community workflow feature #95

This PR partially addresses our requirements around reviewer workflow by requiring that all records are members of a community. This was added as an InvenioRDM feature to invenio-rdm-records v10.9.0.

Developer Checklist

Developers should review and confirm each of these items before requesting review

• Code meets acceptance criteria from issue
• Unit tests are written and all pass
• User Test Scripts (if required) are written and have been run through
• Code documentation and related non-code documentation has all been updated

Reviewer Checklist

Reviewers should review and confirm each of these items before approval
If there are multiple reviewers, this section can be duplicated for each reviewer

• Code meets acceptance criteria from issue
• Unit tests are written and all pass
• User Test Scripts (if required) are written and have been run through
• Code documentation and related non-code documentation has all been updated
• Migation has been created and tested

Testing

List user test scripts that need to be run

List any non-unit test scripts that need to be run

[J4bbi]

@cc-a this will break importing the test data, how do you want to resolve that?

[Steven-Eardley]

I suggest we ignore it breaking the data import script, and modify that as required once we have a community to target.