Editor: Update RichEditor to use inputValue

[Samk13]

❤️ Thank you for your contribution!

Description

This will fix the editor's loss of content after losing focus in communities invite modal
Closes inveniosoftware/invenio-app-rdm#2771
Related to inveniosoftware/react-invenio-forms#249

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.

[max-moser]

basically the same change as in inveniosoftware/react-invenio-forms#249, which fixed an issue where the editor lost its content when it lost focus

[max-moser]

with some quick testing (of the community member invitation modal) on a local v13 i couldn't find the issue of the editor losing content when losing focus.
however, i could find this issue in a v12 setup and this PR (backported) fixed that.
on v13, i could not detect any adverse effects with this PR.

[Samk13]

with some quick testing (of the community member invitation modal) on a local v13 i couldn't find the issue of the editor losing content when losing focus. however, i could find this issue in a v12 setup and this PR (backported) fixed that. on v13, I could not detect any adverse effects with this PR.

From my testing, this issue appears to be flaky, it sometimes works and sometimes doesn't, which was confusing. Therefore, I've decided to keep this change for now, as it guarantees the functionality.
Unless a cleaner solution is found, we'll proceed with this for now.
For the failing CI I added this one: #1186 so no need to worry about it.

[max-moser]

alright, thanks for the extra infos!
as an immediate fix, i just replaced docker-compose --version with docker compose version.
when the CI actions get reworked, this will be replaced anyway :)