Migrate codebase to React 18

[mirekys]

❤️ Thank you for your contribution!

Description

Migrate react-invenio-forms from React 16 to React 18 following RFC inveniosoftware/rfcs#112.
This PR contains application of following codemods for v18:

• Upgrades peer dependencies
• Replaces enzyme adapter for React18 suppoort
• Removes explicit React imports (update-react-imports codemod)
• Migrates render-only class components to functions (pure-component codemod)
• Updates entry points to createRoot (update-react-imports codemod)
• Bumps Node - >= v22

Prerequisites

To make React 18 linting work, you need to link a local clone of eslint-config-invenio:

gh repo clone inveniosoftware/eslint-config-invenio
gh pr checkout 20
cd eslint-config-invenio
npm link

In this repo:

npm link @inveniosoftware/eslint-config-invenio

Status:

• All tests pass

Requires:

• config: add React 18 ESLint configuration eslint-config-invenio#20 (must be merged & released first)
• ci: migrate to shared workflows #335
• components: remove defaultProps from components #336

Part of: inveniosoftware/rfcs#112

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.

[ntarocco]

Same comment as in RSK, is it possible to keep React v16 as min version?

[mirekys]

Same answer as in RSK, while not entirely impossible (with 18, apps will still probably run, in "legacy" mode, throwing a lot of deprecation warnings), it would be harder to support both 16 and 18, plus it would effectively block any new React 18 features adoption. It would mean we just enable integration of modern npm packages with RDM (having peer deps requiring react >=18). But our codebase basically stays the same as it is now with 16.