chore(version): bump to 0.9.0.3

[romeokienzler]

What

Bump the package version 0.9.0.2 → 0.9.0.3.

Why

0.9.0.2 was already consumed (a build under that version was produced but not published cleanly), so it is burned. This bump lets the vLLM-0.29 serving support already on main be published to PyPI as 0.9.0.3.

Scope

Version bump only — no functional changes over 0.9.0.2. The PF .static backfill fix (#125) is intentionally not included here and will ship in a later release.

Once merged, a v0.9.0.3 tag on the resulting main commit triggers the release workflow to build and publish to PyPI.

🤖 Generated with Claude Code

[romeokienzler]

@romeokienzler thanks — this is a clean, minimal version bump (0.9.0.2 → 0.9.0.3 in pyproject.toml, no functional changes), and it reads correctly against the PR intent.

What's needed

• Nothing substantive from you. DCO is signed off ✅, and the completed security scans (Bandit, CodeQL, Trivy, detect-secrets) pass. No new params/deps/docs are implied by a version bump, so the config-YAML and docstring checklist items don't apply here.
• Just let the remaining checks finish — pre-commit-run, pytests, CodeQL (Python), and security are still pending. If pip-audit (deps) comes back red, that's the known repo-wide PYSEC-2026-3624 (lightning) blocker being fixed separately, not anything wrong with this PR.
• One thing to confirm before tagging: per the description the v0.9.0.3 release tag should land on the resulting main commit so the release workflow publishes cleanly.

Looks ready for a maintainer's look once CI is green.

— 🤖 _automated pre-review; a maintainer will follow up_