The source distribution on pypi is created with setuptools and therefore has access to the repository, so you could use e.g. setuptools_scm to write the current version to a .gitignore'd file. Even though this is possible, I'd recommend tracking the version explicitly in the code and/or build configuration. Modern build tools such as flit and poetry do even mandate this.

Pip uses the source distribution published on pypi, which is basically the repository contents without the .git folder (but with some extra metadata) so the setup.py can't use git to determine the version. Most projects either set the version in setup.py explicitly or as a constant in the source code which they import at build time. It would IMO also be very good to also publish wheels to pypi, which do not need to be build to be installed. (It's not more work than installing wheel and running bdist_wheel before uploading)

No, I'd like to see directly in https://query.wikidata.org what the json will look like so I can write my application accordingly. The final application will then of course use the API. Having this directly in the web interface would make developing easier and faster and should be to implement (just add a library for pretty printing and add a button in the dropdown).