feat: add python-version input for Python ecosystem

[brendanjryan]

The action currently hardcodes python-version: '3.11' in the setup-python step. This breaks packages that declare requires-python = ">=3.12" in their pyproject.toml — python -m build fails silently because hatchling (and other build backends) reject the Python version.

Changes

Adds a python-version input (defaults to 3.11 for backward compatibility) and uses it in the setup-python step:

- uses: wevm/changelogs@master
  with:
    ecosystem: python
    python-version: '3.12'
    pypi-token: ${{ secrets.PYPI_TOKEN }}

Context

We hit this in tempoxyz/pympp where the package requires >=3.12. The changelogs publish command exits with code 1 and no visible error output because python -m build fails under 3.11 and the error gets swallowed by the 2>&1 capture in the publish step.

[vercel]

@brendanjryan is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.