chore: sync uv.lock with the 0.2.0 release

[cesarenaldi]

The 0.2.0 release-please merge bumped pyproject.toml to 0.2.0 but left uv.lock at 0.1.0, so uv sync --locked fails Static Checks on every push to main.

Regenerates the lockfile with uv lock (only the polymarket-client version entry changes). Verified locally with uv sync --locked.

Follow-up: the release workflow should keep uv.lock in sync when release-please bumps the version, tracked separately.

---

Note

Low Risk
Lockfile-only version alignment with no runtime or dependency resolution changes beyond the local package version string.

Overview
Updates uv.lock so the editable polymarket-client package is recorded as 0.2.0 instead of 0.1.0, matching pyproject.toml after the release-please bump.

This restores uv sync --locked in CI (Static Checks) when the lockfile and project version were out of sync; no dependency graph or application code changes.

^{Reviewed by Cursor Bugbot for commit 2286c68. Bugbot is set up for automated code reviews on this repo. Configure here.}