Add a temporary workaround to get building on Node 18 since Node 16 EOL is 2023-09-11

[tsmock]

This does the following:

• Add NODE_OPTIONS=--openssl-legacy-provider (not needed once we upgrade to react-scripts v5 or remove/replace react-scripts)
• Only adds NODE_OPTIONS when run on node 18 or later
• Performs frontend-code-test on node 18
• Does not run backend_deploy/frontend_deploy with node 18. This can be changed via using cimg/python:3.10-node (versions after 3.10.8-node use node 18 instead of node 16)

Node 16 EOL Notice: https://nodejs.org/en/blog/announcements/nodejs16-eol create-react-app --openssl-legacy-provider: https://github.com/facebook/create-react-app/issues/11562

This is intended to be a temporary fix for #5767.

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.2% Duplication

[dakotabenjamin]

We built some node images for this issue while we work to get TM running on a newer version: https://quay.io/repository/hotosm/node?tab=tags

[ramyaragupathy]

@varun2948 @tsmock - with the node upgrade coming from #5721 merge is this relevant?

cc @royallsilwallz @manjitapandey

[tsmock]

Nope. We can close this.