PyPI upload filename has to match project name

[rsnyman]

I encountered this while attempting to release 1.0.1/1.0.2. Currently, if you build a package and upload it to PyPI via twine, you get the following error:

HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/        
         Start filename for 'widgetastic.core' with 'widgetastic.core'.

Digging into the warehouse code, I discovered that the legacy upload requires the filename to match the project name.

In order to upload the release, I had to build it on my local machine, rename the files, and then upload them. We need to figure out how to get around this issue. I'm not sure why we didn't run into it before.

[LightOfHeaven1994]

@rsnyman this issue was fixed here right?

[rsnyman]

@LightOfHeaven1994 No, actually, PyPI wants the filename to be "widgetastic_core"

[RonnyPfannschmidt]

Recent tools should actually use normalized upload names

It may be helpful to switch to hyneks build-and-inspect-python-package + the most recent upload actions of pypa

[digitronik]

I think this is due to the new PEP-427.

It's not an issue with PyPI, it asks for what package name we put initially i.e. widgetastic.core but
currently hatch building widgetastic_core-1.0.3-py3-none-any.whl which creates a problem.

We need to figure out a better solution.

ref: https://github.com/RedHatQE/widgetastic.core/actions/runs/5388878711/jobs/9782094368
ref: https://discuss.python.org/t/amending-pep-427-and-pep-625-on-package-normalization-rules/17226/32?page=2

[mshriver]

This gets us out of the blocked upload on legacy, but we can still consider setting the package name to be normalized per:
https://packaging.python.org/en/latest/specifications/name-normalization/