[TODO] Figure out why TestPyPI rejects sdist uploads

@Jakuje reported CI/CD failing on merge. It turned out that automatic publishing to PyPI was partly failing — it'd upload 20 wheels but fail on sdist. I've looked at a few last releases on TestPyPI and they apparently lack sdists: https://test.pypi.org/project/ansible-pylibssh/1.3.1.dev50/#files. The last one with an sdist was on Oct 21. This raises a suspicion that needs investigating. The CI/CD runs have indeed started failing matching the timeline of missing sdist releases: https://github.com/ansible/pylibssh/actions/workflows/ci-cd.yml?query=branch%3Adevel+event%3Apush. Our DumbPyPI index received an sdist so it is not getting lost in the GHA artifacts: https://ansible.github.io/pylibssh//simple/ansible-pylibssh/. So it's likely that PyPI somehow chokes on sdists and we'll need to figure out why. We may be hitting an overall limit per-release. Though our releases contain roughly 50 MB of artifacts so this is unlikely. Action items: * [ ] Enable verbose output in `pypi-publish` * [ ] Enable printing out the hashes in `pypi-publish` * [ ] Decide what's next