chore(version): set version to 0.9.0.2

[romeokienzler]

Sets the declared package version to 0.9.0.2 instead of 0.9.1.

main and feat/vllm-0.29-support both currently declare version = "0.9.1", but the last release published to PyPI is 0.9.0.2. This aligns the source-tree version with the released one.

Single-line change in pyproject.toml (the only version reference in the repo).

🤖 Generated with Claude Code

[romeokienzler]

@romeokienzler thanks for the tidy version-alignment PR — clean, single-line, scoped to just the metadata, signed off (DCO ✅), and the AI-assist disclosure is appreciated. I confirmed pyproject.toml:12 is indeed the only package-version reference in the tree (the version keys in io/config_version.py are the separate config-schema version, not this one).

What's needed

• Confirm the version direction is intended. Under PEP 440 ordering 0.9.0.2 < 0.9.1, so this is technically a version decrease. That's fine if the goal is purely to re-sync the source tree with the last released tag before cutting the next release — just wanting to make sure it's deliberate and not that a 0.9.1 was already published (I couldn't reach PyPI from here to verify the "last release = 0.9.0.2" claim, so a maintainer should double-check against the actual PyPI history).
• Checks: most are still pending; nothing failing that's on you. Note the repo-wide pip-audit failure (PYSEC-2026-3624 / lightning) is a known infrastructure blocker being fixed separately — not your fault and not something this PR needs to address.

Otherwise this looks ready for a maintainer's look — no tests/docs/config changes are warranted for a pure metadata bump.

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