Set compilerOptions.jsx = "react"

[alx-khramov]

Typescript offers various jsx compiling options.
This PR sets compilerOptions.jsx field to use legacy react value instead of react-jsx.
Other changes are just side effects of this action.

Reason:

Currently, we use React v17 on Lido widgets, and reef-knot also supports React v17.
React v17 has an issue with ESM because it has no exports field in the package.json.
This can cause such error during building a based on react v17 project, which uses ESM and imports reef-knot:

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '<...>\node_modules\react\jsx-runtime' imported from <...>
Did you mean to import react/jsx-runtime.js?

It happens because of the way how ESM in node.js is defined. In modules with a package.json containing "type": "module" imports in .mjs or .js files must be fully specified (with extensions), or it can be solved by the exports field.

It worked before because reef-knot was built as a CJS module.
The issue is fixed in react v18 – they've added the exports field to package.json, so we can switch back to react-jsx option after migrating to react v18.

More info:

• Bug: Cannot import 'react/jsx-runtime' from esm node/webpack 5 facebook/react#20235
• Add flight specific entry point for react package facebook/react#20304
• Compiling error with NextJS 11.1.0: Did you mean to import react/jsx-runtime.js adazzle/react-data-grid#2568
• build: updates to support Node ESM aws-amplify/amplify-ui#3287 (comment)
• webpack 5.0.0-beta.30 Module not found: Error: Can't resolve '../../core-js/object/define-property' webpack/webpack#11467 (comment)