Update workflows to use Node.js v16

[robwalch]

This PR will...

• Update workflows to use Node.js v16.

Why is this Pull Request needed?

Testing functional test hosting in updated Node.js

Checklist

• changes have been done against master branch, and PR does not conflict
• new unit / functional tests have been added (whenever applicable)
• API or design changes are documented in API.md

[robwalch]

@tjenkinson I was hoping that updating Node.js would resolve the issue with running functional tests on Safari with http-server - following up from #4812. I guess not.

[tjenkinson]

Makes sense to update to 16 anyway 👍

Don't have much time atm but can look into that error. Did you hear back from saucelabs?

[robwalch]

I did not hear back. It looks like a driver issue running the browser.executeAsyncScript call that kicks off the test:

  {
    "screenshot": null,
    "suggestion_values": [],
    "start_time": 1659385362.004201,
    "request": {
      "args": [
        "https://test-streams.mux.dev/x36xhzz/x36xhzz.m3u8",
        {}
      ],
      "script": "return (function (url, config) {\n    const callback = arguments[arguments.length - 1];\n    self.startStream(url, config, callback);\n    const video = self.video;\n\n    video.onloadeddata = function () {\n      callback({\n        code: 'loadeddata',\n        logs: self.logString\n      });\n    };\n  }).apply(null, arguments);"
    },
    "result": {
      "message": "POST /session/A8B8D1C7-3F28-4C6B-B2E1-826E5F550042/execute/async\nBuild info: version: '3.14.0', revision: 'aacccce0', time: '2018-08-02T20:13:22.693Z'\nSystem info: host: 'itako757.prod.miso', ip: '10.125.1.55', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.15.4', java.version: '13.0.1'\nDriver info: driver.version: unknown",
      "error": "unknown command",
      "stackTrace": [
        {
          "className": "org.openqa.selenium.remote.http.AbstractHttpCommandCodec",
          "lineNumber": 261,
          "methodName": "decode",
          "fileName": "AbstractHttpCommandCodec.java"
        },

The request looks identical to passing tests on other platforms. My guess is the keyword self is an issue here. Let's see...

[robwalch]

The request looks identical to passing tests on other platforms. My guess is the keyword self is an issue here. Let's see...

That wasn't it. I'll roll back that change and merge the node.js update.