Add PyPI checker and issue creator

[anthonykim1]

Resolves: #22800

[karthiknadig]

@anthonykim1 What we really need here is have a workflow that runs once a week. that workflow should install packages with --pre for pip. Then run our python test suite on it. If it fails, then create an issue.

If it creates an issue on every pre-release that will be a lot of noise. I think it should do this only if the python tests fail.

[anthonykim1]

Now mainly having two condition to trigger issue creation in Python Repo:

1. There is newest version (including pre-releases) of Pytest that is different from what we have. This won't be too much of a noise since cron job runs once a week as recommended.
2. Python tests fails with the --pre with pip installs.

[karthiknadig]

Why is pytest imported here? it won't even be installed when this script is actually called.

[anthonykim1]

I thought we would need this for importlib.metadata.version("pytest") to correctly fetch the version of pytest that is imported.
Should I add pytest in additional to python -m pip install -U pip wheel PyGithub or do we not need it at all??

[karthiknadig]

In your pipeline you are not installing pytest. import pytest will immediately fail. This works for you locally because you have pytest installed locally. Try running this from a fresh environment.

[karthiknadig]

If you need pytest then you need to install all requirements before running this script. In this script you can later update the installed pytest to whatever version you want.

[anthonykim1]

I see... the intent of importing pytest and running importlib.metadata.version("pytest") was to get the version of pytest that our python extension was using...

Now I'm little lost on how to correctly get this value.

[anthonykim1]

Now I install test-requirement.txt and then use importlib to dynaimically get it since test-requirement.txt does not pin to specific version of pytest.

[karthiknadig]

Closing this since this hasn't been worked on in a while