PyPI release is stale and version never bumped (both builds report 0.1.0)

[mspinola]

Problem

The version in pyproject.toml is still 0.1.0, but the code has advanced far past what's published on PyPI. Installing from PyPI gives a build that lacks the current producer/databento CLI:

$ pip install "cotdata[norgate]"
$ cotdata-update --prices --metadata
cotdata-update: error: unrecognized arguments: --metadata

The repo's src/cotdata/update.py defines --metadata, --require-final, --final-cutoff, --ingest-databento, --build-databento, --full, --check, --reconcile, --prices-yahoo, etc. — none of which exist in the PyPI 0.1.0 build. So anyone who follows the setup docs' pip install path gets a package that imports fine, reports version 0.1.0, and then errors on the documented commands.

Two compounding issues:

1. PyPI is stale — the published artifact predates the databento producer work (ADR-0006), the ingest hardening, and the --require-final price workflow.
2. The version was never bumped, so the stale PyPI build and a fresh editable clone install both report 0.1.0. The version string is useless for telling them apart — you have to inspect cotdata-update --help.

Impact

• The Windows setup guide had to be changed to install editable-from-clone instead of PyPI (Install Windows cotdata editable from clone (PyPI 0.1.0 is stale) #47), because the documented pip install "cotdata[norgate]" producer path is broken.
• Any downstream pip install cotdata consumer is pinned to long-obsolete code with no signal that they're behind.

Proposed fix

1. Bump the version in pyproject.toml to something clearly ahead of 0.1.0 (e.g. 0.2.0), matching the current CLI surface.
2. Publish a fresh release to PyPI.
3. Once published, revert the Windows setup guide (Install Windows cotdata editable from clone (PyPI 0.1.0 is stale) #47) back to plain pip install cotdata / pip install "cotdata[norgate]" for the non-development cases, and drop the "PyPI is stale" warning.
4. Consider a release checklist / CI gate so the PyPI version can't drift this far behind main again (e.g. fail CI if pyproject.toml version is unchanged when the CLI surface changes, or a tag-triggered publish workflow).

Repro

pip install "cotdata[norgate]"        # pulls PyPI 0.1.0
cotdata-update --help                 # note: no --metadata / --require-final
python -c "import cotdata; print(cotdata.__version__)"   # 0.1.0

vs. an editable install from a current clone, which reports the same 0.1.0 but has the full CLI.