Change AppVeyor to test more versions, no wheels

We already generate wheels in our GitHub Actions via cibuildwheel, so
there's no need to generate them in AppVeyor anymore (we used to when we
manually generated wheels for different platforms). On the flip side, we
can test against more python versions, and only focus on 64-bit builds.

Keeping AppVeyor around is still a good thing, as it gives us quick
feedback if there's something broken with a build on Windows without the
overheads of cibuildwheel.

Signed-off-by: Rodrigo Tobar <[email protected]>

Author: rtobar

.appveyor.yml

@@ -5,23 +5,25 @@
 # Copyright by UWA (in the framework of the ICRAR)
 # All rights reserved
 
+image: Visual Studio 2019
+
 environment:
 
   matrix:
 
     # For Python versions available on Appveyor, see
     # http://www.appveyor.com/docs/installed-software#python
-    - PYTHON: "C:\\Python35"
-    - PYTHON: "C:\\Python36"
-    - PYTHON: "C:\\Python37"
-    - PYTHON: "C:\\Python38"
     - PYTHON: "C:\\Python35-x64"
+      APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2015
     - PYTHON: "C:\\Python36-x64"
     - PYTHON: "C:\\Python37-x64"
     - PYTHON: "C:\\Python38-x64"
+    - PYTHON: "C:\\Python39-x64"
+    - PYTHON: "C:\\Python310-x64"
+    - PYTHON: "C:\\Python311-x64"
 
 install:
-  - "%PYTHON%\\python.exe -m pip install wheel pytest"
+  - "%PYTHON%\\python.exe -m pip install pytest"
   - cmd: git submodule update --init --recursive
 
 build: off
@@ -32,8 +34,5 @@ test_script:
   - "%PYTHON%\\python.exe setup.py develop"
   - "%PYTHON%\\python.exe -mpytest -v"
 
-after_test:
-  - "%PYTHON%\\python.exe setup.py bdist_wheel"
-
 artifacts:
   - path: dist\*