chore: bump allocator/client to 0.4.0 and CLI to 0.3.0

[7174Andy]

Summary

Release prep for the next coordinated release. publish-pip.yml's version guardrail rejects a tag whose version does not match pyproject.toml, so the bumps land on main before the tags are cut.

• allocator 0.3.0 → 0.4.0 — feat feat: default the client AMI to a per-region Deep Learning Base AMI #489 (per-region Deep Learning Base AMI default), fix fix(allocator): retry assign_vm when SKIP LOCKED hides a transiently locked seat #499 (assign_vm SKIP LOCKED retry)
• client 0.3.0 → 0.4.0 — lockstep with the allocator, as since 0.1.0
• cli 0.2.0 → 0.3.0 — feats feat(cli): prompt for tunnel credentials when their flags are omitted #485/feat(doctor): warn when an HTTP deployment silently disables H.264 #491, fixes fix: verify the client AMI exists instead of trusting AMI_MAP #484/fix: treat an empty machine.ami_id as the fallback, not a missing value #490, lablink-template pin v0.3.1 (chore(cli): bump pinned lablink-template to v0.3.1 #498)

Changes Made

• Version bumps in the three pyproject.toml files.
• CLI's allocator pin raised >=0.2.0 → >=0.4.0. The CLI re-exports MachineConfig, whose ami_id default became empty (= resolve the per-region Deep Learning Base AMI, feat: default the client AMI to a per-region Deep Learning Base AMI #489) in allocator 0.4.0. Against an older allocator, the wizard would silently write the stale hardcoded us-west-2 AMI into configs and doctor's fix: treat an empty machine.ami_id as the fallback, not a missing value #490 empty-AMI fallback path would never fire — no ImportError would flag it.
• packages/cli/CHANGELOG.md: new 0.3.0 section (fix: verify the client AMI exists instead of trusting AMI_MAP #484, feat(cli): prompt for tunnel credentials when their flags are omitted #485, fix: treat an empty machine.ami_id as the fallback, not a missing value #490, feat(doctor): warn when an HTTP deployment silently disables H.264 #491, chore(cli): bump pinned lablink-template to v0.3.1 #498) and a backfilled 0.2.0 – 2026-08-31 section — chore: bump allocator/client to 0.3.0 and CLI to 0.2.0 #481 tagged 0.2.0 without adding one (refactor(cli): route every manual-deployment fact through one manual.py module #467, feat(cli): external-runtime deploy mode (--render-only) — run the allocator on Run:AI/K8s without Docker #472, fix(cli): warn about Let's Encrypt's 5-certs/7-days rate limit in wizard and deploy #474, feat: BYO clients ship their own container logs; drop the CLI's detached shipper #479).
• README's Docker <version> tag example moved to 0.4.0 (same convention as chore: bump allocator/client to 0.3.0 and CLI to 0.2.0 #481; the PyPI shields badges need no edit).

Testing

• No code changes; uv lock resolves the workspace cleanly with the new versions and the raised pin.

Release order after merge

Tag allocator → client → cli (lablink-<pkg>_v<version>, matching pyproject exactly). The raised pin also enforces allocator-first at install time.