wheel build improvements

[behrisch]

the new cibuildwheel workflow works already quite well but the following points are still open

• should we provide the wheels we build on our build servers (https://sumo.dlr.de/daily/wheels) as well or do we rely on ci?
• proj.db should be included everywhere Always provide proj.db in binary releases #17457
• check why windows tests do not work when libsumo is in a virtualenv
• check whether the sumo-data approach can be extended to macos / linux create sumo libraries wheel #12770
• check whether we want to use the python stable ABI to reduce the number of wheels we need to provide (there seems to be some swig support for it)
• replace the existing wheel builds for linux and windows by calls to cibuildwheel keeping possible additional steps
• add workflows which download the wheels from sumo.dlr.de / pypi and test them
• check automatically whether those wheels are actually the most recent ones we expect
• make sure build and test work on the same commit (the repo gets cloned twice in the process)
• always build sumolib / traci wheels when running only a single os
• remove all setup.py build infrastructure and update the docs to speak only about pyproject.toml
• fix differences in the results on mac and ARM linux check platform differences with ARM #17458
• check whether we should build and ship language bindings for C# and Java in the wheels
• add basic sumo-gui and netedit tests