AppVeyor: Test and support versions 8, 10, 12, 14, 16, 17, 18, 19, 20, 21, and 22

[cclauss]

Tested versions 8, 10, 12, 14, 16, 17, 18, 19, 20, 21, and 22.

Test supported Node.js versions before unsupported versions because each test takes ~5 minutes.
Test on the most current Visual Studio possible for each nodejs_version.
Test on the oldest supported Python version when possible (currently py39).
For all supported Node.js versions also test on the newest Python (currently py313).

• https://devguide.python.org/versions

Test results: https://ci.appveyor.com/project/RodVagg/nan

Visual Studio 2017 image tops out at Python 3.8 which is end-of-life.
Visual Studio 2019 and 2022 images top out at Python 3.13.

node-gyp issues related to nan: https://github.com/nodejs/node-gyp/issues?q=label%3Anodejs%2Fnan

The Node.js v23 tests are commented out waiting for:

• Support Node 23 #979 or similar.

The Python 3.12 and 3.13 tests are commented out waiting for:

• package.json: Upgrade node-gyp to support Python >= v3.12 #985 because of:
  • distutils is removed in Python 3.12 node-gyp#2869

@kkoopa Your review, please. These changes enable us to focus on the two issues above.

[kkoopa]

Thank you. This looks good to me. While I do not think testing on multiple Python versions for the sake of testing Python is necessary, I do not see it hurting apart from longer runtimes. The reason for originally specifying multiple Python versions was just to get it all working with various images and versions.

[cclauss]

I do not think testing on multiple Python versions [ ... ] is necessary.

The real problem is

• AppVeyor tests fail on Python 3.12 and 3.13 #986 which is fixed (and autoclosed) by the one-line change in
• package.json: Upgrade node-gyp to support Python >= v3.12 #985 which is the cause of numerous nan-related issues being raised on the node-gyp repo that I co-maintain.

Please review and merge #985 and make a new npm release.

If long test runtimes (2+ hours) is an issue then please review and merge

• GitHub Action to run tests on most versions of Node.js #957 so that the CI tests run in parallel instead of serially.
  • ~6 minutes for ALL tests to run instead of ~6 minutes per test over and over again --> ~2 hours 20 minutes.

[cclauss]

@kkoopa Your review, please. This puts README.md, AppVeyor, and GitHub Actions in sync on which versions to test.