Bump Base to the published base-cli 0.2.0 release

[codeforester]

Context

Base currently pins base-cli==0.1.0 in requirements-dev.txt, but its source and CI now require the consumer-neutral API shipped after the refactor, including CliProfile, register_record_schema, and CommandFilterNormalizer.

The reusable base-check workflow installs requirements-dev.txt without checking out a base-cli sibling, so the stale PyPI package can crash source-checkout mode even though the normal Base test jobs shadow it with a source checkout.

Scope

• After base-cli Standardize Bash helper filenames on .sh #33 publishes 0.2.0 to PyPI, update requirements-dev.txt from base-cli==0.1.0 to base-cli==0.2.0.
• Keep source-checkout CI coverage intact; the normal test jobs may continue to use the pinned base-cli source checkout for source-level testing.
• Verify the reusable base-check workflow in source-checkout mode with no sibling base-cli checkout or BASE_CLI_SOURCE_DIR override.
• Run the full applicable Base test and security suites, including the installed-provider path.
• Add or update a contract check if needed so the pinned distribution cannot silently fall behind the API Base imports.

Dependency

Blocked until basefoundry/base-cli#33 has published base-cli==0.2.0 and its clean-environment API smoke test passes.

Acceptance criteria

• Base no longer pins base-cli==0.1.0.
• A clean source-checkout Base check resolves the published package and starts successfully without a sibling base-cli checkout.
• Existing source-checkout and adapter tests remain green.
• The dependency version and installed API contract are covered against future drift.