Publish llm-d-latency-predictor to PyPI to reserve package name

[RishabhSaini]

Problem

llm-d-latency-predictor is not published on PyPI. This creates a name-squatting risk — anyone can register this name on PyPI and upload a package under it.

If you don't upload to PyPI, then anybody can grab the name. If they upload anything remotely useful, then you may never be able to get it back. A PEP 541 request to reclaim a name can take months to over a year.

Recommendation

Publish an official sdist and wheel to PyPI for each release. This:

1. Reserves the package name before someone else claims it
2. Makes pip install llm-d-latency-predictor work
3. Follows Python packaging best practices

TODOs

• Create a PyPI account or org for the llm-d project
• Generate a PyPI API token
• Add a GitHub Actions workflow to auto-publish on release tags (e.g. using pypa/gh-action-pypi-publish)
• Fix pyproject.toml version to match release tags (fix: update pyproject.toml version to match release tag v0.8.0 #38)
• Build and upload the initial release (python -m build && twine upload dist/*)
• Decide ownership / maintainers for the PyPI package

[fuddin-bit]

/assign