update node to latest LTS & other packages

[huss]

Description

Another housekeeping PR that updates node and npm.

Thanks to @spearec for doing the work to figure out how to get rid of a number of issues and upgrade other packages. A substantial part of the work in this PR is due to @spearec. This upgraded React/Redux packages and TypeScript along with needed code changes.

Updated eslint packages for new TypeScript version.

Workaround for GitHub actions issue with git permissions so checks/tests can run.

Fixes #990.

Type of change

• Note merging this changes the database configuration.
• This change requires a documentation update

Checklist

• I have followed the OED pull request ideas
• I have removed text in ( ) from the issue request

Limitations

Developers will need to delete the web container/image to see this change.

Ignores TS errors for some older, non-hook components but they should go away soon.

[spearec]

Trying to build this gives me a build fail. I think the only reason the git build is passing is that, as per the comment, the git workflow in build.yml was not updated.

Error from npm:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @formatjs/intl@1.17.0
npm ERR! Found: typescript@4.4.4
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"~4.4.4" from the root project
npm ERR!   peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from tsutils@3.21.0
npm ERR!   node_modules/@typescript-eslint/eslint-plugin/node_modules/tsutils
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/eslint-plugin@5.10.0
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       dev @typescript-eslint/eslint-plugin@"~5.10.0" from the root project
npm ERR!   5 more (tsutils, tsutils, react-intl, @formatjs/intl, ts-loader)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^4.5" from @formatjs/intl@1.17.0
npm ERR! node_modules/@formatjs/intl
npm ERR!   @formatjs/intl@"~1.17.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^4.5" from @formatjs/intl@1.17.0
npm ERR!   node_modules/@formatjs/intl
npm ERR!     @formatjs/intl@"~1.17.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /root/.npm/_logs/2023-05-31T13_21_05_144Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-05-31T13_21_05_144Z-debug-0.log

Deleting the OED container and trying to rebuild also failed, so I think that just changing the node dependency breaks quite a bit.

[huss]

Hi @spearec. Did you delete both the container and the image? If I recall correctly, you will see the build create the new node version after that. I realize now that my comment in the limitation was not completely clear. Let me know and I'll look into this if needed.

[spearec]

I believe I have properly installed Node LTS on my fork. The issue seemed to be related to having outdated react and typescript packages, causing conflicting dependencies.
https://github.com/spearec/OED/tree/react_18

[huss]

@spearec was able to install but did see an issue with permissions in VSC. If anyone else sees this then please let us know. This is now ready to merge.