Passing more context to permissions and components

[xsenyaaax]

Description

At CESNET we extend record service in the following ways:

• A community is required when record is created and user has to have a submitter role in that community
• Publishing and similar operations are always performed via dedicated requests, not direct API calls

In order to do so, we need to extend permission checks so that they not only include record but also create/update data and additional parameters from context.

This pull request:

• add kwargs to service methods
• passes the kwargs data and additional context to permission checks

This change is 100% backwards compatible and in RDM does not cause any differences in permission handling. This pull request is also similar to this one in invenio-requests, in which @mesemus provided an explanation.

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 on Discord.

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.