Fix: Update requirements to fix broken package metadata

[ModeSevenIndustrialSolutions]

Fixes the error with the v1.11.0 release:

Uploading distributions to https://test.pypi.org/legacy/
ERROR    InvalidDistribution: Metadata is missing required fields: Name,        
         Version.                                                               
         Make sure the distribution includes the files where those fields are   
         specified, and is using a supported Metadata-Version: 1.0, 1.1, 1.2,   
         2.0, 2.1, 2.2, 2.3.

I've been unable to update to the v1.12.x releases so far, due to issues with some of the recent changes. Porting these fixes back to the v1.11.x branch will be helpful for those of us currently blocked on upgrading. Would you consider merging this pull request and tagging a v1.11.1 release?

[webknjaz]

Hello, I don't have a process or a plan to maintain multiple release streams. I can't even find time to get to releasing a few things that are currently in the unstable branch, adding to that would be rather unhelpful..

OTOH, if it's temporary, you could use your fork just as well. Have you considered doing that?

[ModeSevenIndustrialSolutions]

I understand the problems maintainers face with regard to limited time/resources; I already noticed that the last tagged release (v1.12.4) was back in January. The changes to the Docker container setup in the 1.12.x releases have given me some headaches as a downstream consumer of this action. I have already tested this pull request in my fork, and temporarily repointed my workflows to consume it. I don't have any experience (yet) with Node.js/Javascript based actions, otherwise I'd volunteer to help out with the development/maintenance of your action. I think it's extremely valuable to the Python developer community. As things stand right now, I have a requirement to wrap some additional logic around the PyPI package publishing in a composite action; this is to either leverage trusted publishing, or fallback to static credentials (either in a 1Password vault, or GitHub secrets) when the initial publishing for a new package takes place. Unless I can get the more recent 1.12.x releases working with this constraint, I am probably stuck between a rock and a hard place. Feel free to close/reject my pull request if you can't accommodate it at this time.

[webknjaz]

I think I may be able to make an exception this one time.

[ModeSevenIndustrialSolutions]

@webknjaz
Full disclosure; I actually work for the Linux Foundation (Release Engineering Team) and I'd like to offer to help with the maintenance/development of your action. I'll reach out to you directly to discuss further.