Editor: Update RichInputField to use inputValue instead of value

[Samk13]

:heart: Thank you for your contribution!

Description

• Added missing initialValue prop for RichInputField
• Update prop value to inputValue
• This will fix the input text issue in deposit pages, and communities settings pages
• Request comments work as expected.

Communities Invite members still need to be fixed

Closes https://github.com/inveniosoftware/invenio-app-rdm/issues/2771

I'm currently on vacation, from a quick test when I changed inputValue to a function in the RichEditor instead of the RichInputField, it caused request comments to not clear the input after submission. This PR satisfies all editors except the "community members invite" editor, for which I can submit a similar fix if we agree.

Note : By providing the input value as a function instead of a string, it will fix the render issue. However, this will result in the console error: "Invalid prop value of type function supplied to Editor, expected string."

Feel free to implement a better solution if found.

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.