React imports 2

[zoran995]

What this PR does

Fixes: #7514
Supersedes the #7347, created new PR so build and deployment are available for testing
Small step toward #6538
Run upgrade-react-imports codemod to update react imports so they can work in react 17/18. Partially supersedes #7051.

Don't worry about merge conflicts first PR is only changes by codemod so it is easy to recreate

Test me

Tested locally yarn gulp build. All tests passes. Running the app locally works

Checklist

• There are unit tests to verify my changes are correct or unit tests aren't applicable (if so, write quick reason why unit tests don't exist)
• I've updated relevant documentation in doc/.
• I've updated CHANGES.md with what I changed.
• I've provided instructions in the PR description on how to test this PR.

[pjonsson]

I don't see any version updates in this PR, so I'm guessing a corresponding PR in the TerriaMap repository can be merged independently of this PR?

[zoran995]

@ljowen I have rebased this after the latest UI changes.

[pjonsson]

@zoran995 I hadn't looked at the details of this PR but I just did a git grep "React\." on latest main and there are still quite a few hits. Will things work as intended despite removing the React import?

[zoran995]

The React team recommends using named imports, which works because of automatic JSX support in Babel and TypeScript. When using automatic JSX, Babel and TypeScript detect the JSX syntax in the file and add import React from "react" in the background. Things like React.ReactNode, React.FC, and similar are only types that work in TypeScript due to automatic JSX so TypeScript knows about them without explicit imports.