Implementation of RFC 0072 - Uppy uploader UI for pluggable transfer types

[mirekys]

❤️ Thank you for your contribution!

Description

This PR implements UI changes from RFC 0072 - introduction of pluggable transfer types. It provides
option to use Uppy.io uploader, leveraging the Multipart TransferType instead of standard RDM uploader UI.

Note: needs inveniosoftware/invenio-rdm-records#1930

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.

[utnapischtim]

for me a bool configuration variable should be called with suffix _ENABLED. if we want to use it as it is it should get a string where we have the option for two literals: Literal["multipart", "singlepart"], so the idea is that we could add more options afterward. i am not sure if we need this possibility

[mirekys]

Thanks Christoph, good point, I'll add the suffix. This uploader implementation is meant as a toggleable replacement to the current one, while supporting multiple transfer types (Uppy determines whether to use singlepart or multipart transfer per each individual file, depending on its fsize). As for the second approach, enumerating allowed transfer types (I'm also not sure if there's a case for prohibiting multipart uploads?), uploader UI has already knowledge of it from: https://github.com/inveniosoftware/invenio-app-rdm/pull/2994/files#diff-a779205cb118ac986e91089f0dcc0ed648e4b7a32b252151438c76a8fab7f10fR390-R391, populated by config key: https://github.com/inveniosoftware/invenio-records-resources/pull/604/files#diff-ba4a689688ee572bffc8d2dccf376ed194810cc1ba8e32b6df22832d2acc9ebeR29-R35