Patch Javascript Build Packages

[kwokcb]

Updates

• Fix the packages used for MaterialXTest and MaterialXView so that they are compatible with the current version of NodeJS used (16.20.2).

• The default emscripten 2.0.20 utility script sets NodeJS version to a version which is too old and will result in possible incompatibilities.

• Lock the packages versions until such time as NodeJS version is changed.

  • This will avoid new package versions from accidently being installed (via npm install) which has already occurred.
  • For example the build / tests / installs using packages for NodeJS 18 will not work as the current code is not compatible with changes from 16 to 18.

• Note This does not try to bump any version of emcripten or NodeJS, it just fixes so that the appropriate packages are now used.

• Fixes: Web Viewer : Packages are incompatible using Node version 16. #2547, WebPack Packages are incompatible (won't run) for MaterialXView #2545

Tests

• Cleaned out node modules and rebuild locked package manifest.
• Rebuilt, tested and run on Windows local and via CI. CI no longer shows any warnings / error messages.

Documentation

• Updated with appropriate NodeJS version information
• Fix documentation for emscripten version as not any verson can be used. Note the locked version require.

[kwokcb]

@ashwinbhat , @jstone-lucasfilm : I'm not sure if it's too late for this change, but I think it would be better to patch this to have a known safe version of the packages used for the JS build.

[kwokcb]

Lock these to avoid version "creep". New versions can make it so that tests won't run.

[kwokcb]

Fix this as version "creep" has already occurred. This is 100% compatible with the NodeJS version we are locked on for builds (16.20.2). I set this to test locally on Windows.

[kwokcb]

This should never have been used as newer versions can be incompatible and not build the C++ code due to API changes.

[jstone-lucasfilm]

This change sounds very reasonable to me, @kwokcb, though since it's a significant number of edits, I'd feel more confident waiting until 1.39.5 to move forward with this.