fix: removing dependancy for node-requests

[manchuck]

This PR removes the 'requests' package, which has not been updated in over 6 years and has major security errors.

[codecov]

Codecov Report

Merging #311 (a3a4b34) into main (111be34) will increase coverage by 16.6%.
Report is 3 commits behind head on main.
The diff coverage is 74.3%.

Files	Coverage Δ
spec/opentok_spec.js	100.0% <100.0%> (ø)
lib/moderation.js	93.1% <88.8%> (-2.6%)	⬇️
lib/signaling.js	88.8% <90.9%> (ø)
lib/client.js	78.8% <82.7%> (-0.2%)	⬇️
lib/opentok.js	76.4% <28.5%> (-0.4%)	⬇️
lib/render.js	19.6% <12.5%> (-2.0%)	⬇️
lib/callbacks.js	74.6% <77.1%> (+1.6%)	⬆️
lib/archiving.js	75.4% <77.2%> (+66.8%)	⬆️

... and 1 file with indirect coverage changes

[jeffswartz]

Some tests in opentok_spec.js are failing.

[jeffswartz]

Some tests are failing: #311 (review).

Also, please rev the version (to 2.17.0) in package.json and package-lock.json.

[manchuck]

Some tests are failing: #311 (review).

Also, please rev the version (to 2.17.0) in package.json and package-lock.json.

This should only be requested once the PR is ready to merge in. Otherwise the PR will always be rejected as we paly whack-a-mole with the release versions

[manchuck]

Some tests in opentok_spec.js are failing.

These failures are inconsistent and intermittent. I am not familiar with these tests or how to resolve them. The reason for asking for your review on this PR is because there is not full coverage for all use cases with the SDK. Any guidance from you would be helpful

[jeffswartz]

15 tests are failing ("Archiving listArchives should return an array of archives and a total count" and 14 others).

[jeffswartz]

When I install packages, I am alerted the get-func-name is audited with "high" vulnerability. And @babel/traverse is flagged as being critical. Can we update chai and nyc to update these sub-packages?

[jeffswartz]

We need to rev the version of the library (to 2.16.1) in the package.json and package-lock.json files.

[jeffswartz]

The linter complains that this (and other instances of catch {}) results in a parsing error. (Replace with catch (error) { }).

There are already existing linting errors in the main branch. But if you add /* eslint-env es2018 */ to the top of this file, you will see more linting errors.

[jeffswartz]

Please rev the version (to 2.17.0) in package.json and package-lock.json. (I assume we are ready to release this.)