fix(deps): upgrade eslint to fix semver vulnerability

[roggervalf]

also I think it will solve #207 and #208, as new versions do not depend on semver

[roggervalf]

please @jhnns, when you get some chance

[coveralls]

coverage: 98.721%. remained the same when pulling 697ff71 on roggervalf:fix-semver-vulnerability into f5c655a on jhnns:master.

[roggervalf]

this is weird, I can execute the tests locally without errors

also I tried to update package-lock using version 1, as it was generated with that version

[roggervalf]

so it's failing for node 10 because of this change eslint/eslint#14592 base on eslint/eslint#14023. https://community.sonarsource.com/t/drop-of-node-js-10-support-and-deprecation-of-node-js-12-support/59590 node 10 is no longer being supported, so this should be considered as a breaking change, let me update the ci to drop of node 10 as well

[jhnns]

Thank you for your PR. The failing tests were caused by a breaking change in the package-lock file from npm 8 to 9. I decided to remove official Node 10, 12, 14 and 16 support, as it was not possible to run the CI pipeline with this breaking change.

I made all these changes on the master branch as it was easier for me, so I'm closing this one. The ESLint update shipped with rewire v7.0.0.