deposit-ui: permissions-based record access config

[slint]

Depends on inveniosoftware/react-invenio-deposit#622 and inveniosoftware/invenio-rdm-records#1223.

• Passes config to the upload form based on permissions, to control
  the display of record access and metadata-only toggles.
• Closes deposit: disallow fully restricted records #2022.

❤️ Thank you for your contribution!

Description

Please describe briefly your pull request.

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 (for relevant code).
• I've followed the CSS/JS and React guidelines (for relevant code).
• I've followed the web accessibility guidelines (for relevant code).
• I've followed the user interface guidelines (for relevant code).
• 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).

Third-party code

If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.

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.

[kpsherva]

does it make sense to make it a part of the service class?

[slint]

It feels a lot like a utility function, since service methods usually return ResultItem objects. Another issue is that the record argument has to be an API Record which is difficult to get hold of without calling a service and accessing item._record...

There's a similar method on ResultItem.has_permissions_to, used on the deposit_edit view below, which does exactly that. The issue is that in the deposit_create view, we don't have a draft item result from the service to call it (since we're starting a new one).

It would look something like inveniosoftware/invenio-records-resources#456, but kwargs would need to be low-level objects.