Use newer node version for browser tests and code coverage

[blumamir]

In #1417 I attempted to upgrade the node version used for the browser test from 14 (which is EOL) to 18.

Since we are also running special code coverage workflows in CI for specific node version (currently 14), I think they should be bumped together.

The code-coverage workflow was not producing useful results for a long while, and it is now in the process of being fixed by @chigia001

This issue is to track the task of upgrading our codecov and browser tests to a newer node version.

In my PR #1417 I had to enable this option NODE_OPTIONS=--openssl-legacy-provider to make the build pass, not sure if this should be addressed as NODE_OPTION, or should we use newer dependencies that are compatible with newer node versions for tests?

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.