WSTEAM1-547: Update to Node 18

[shayneahchoon]

Resolves JIRA WSTEAM1-547

Code changes

Changes the following actions to use node 18.x runtime environment:

• .github/workflows/simorgh-e2e-tests.yml
• .github/workflows/simorgh-integration-tests.yml
• .github/workflows/simorgh-local-server-tests.yml
• .github/workflows/simorgh-misc-checks.yml
• .github/workflows/simorgh-release-asset.yml
• .github/workflows/simorgh-unit-tests.yml
• .nvmrc

Compatibility changes:

• Sets the Node flag --no-experimental-fetch, as Node 18 introduces a new fetch mechanism under the hood: https://nodejs.org/en/blog/announcements/v18-release-announce#fetch-experimental. We will likely need to tackle this when we update Next.JS to version 13.x, as it forces usage of the new fetch mechanism
• Updates Lighthouse to version 11.x
• Removes deprecated Expect-CT header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expect-CT
• Removes deprecated prefetch-src header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/prefetch-src
• Above of these headers greatly decrease the bestPractices Lighthouse metric, so they have been removed as they are no longer supported

Also VERY IMPORTANT:

• ramda has been updated to package version 0.29 and part of this change means that the prop order for pathEq/propEq have now changed inline with Ramda docs: Ramda 0.29

Coding Standards

Repository use guidelines

[karinathomasbbc]

Nice work!

[HarveyPeachey]

Did something weird happen here with the commits? There's 88 of them and some back date to May

[amoore108]

Did something weird happen here with the commits? There's 88 of them and some back date to May

Yea we accidentally pulled in changes from my NextJS 13.x upgrade branch, but it has been reverted. The commit history will look weird here but should be squashed when merged.