Publish only tangle-cli artifacts in release workflow

[Volv-G]

Summary

• publish only dist/tangle_cli-* artifacts in the PyPI release workflow
• keep building/smoke-testing tangle-api locally for compatibility coverage, but avoid attempting to re-upload unchanged tangle-api==0.1.0 files

Context

tangle-cli 0.1.1 is a CLI-only release that intentionally depends on the existing tangle-api==0.1.0. Even with --check-url, publishing dist/* can fail if a rebuilt tangle-api 0.1.0 artifact is not byte-identical to the file already on PyPI. Since tangle-api did not change, the release should upload only the new tangle-cli distributions.

After this lands, I will retag v0.1.1 at the fixed master commit to re-run the publish workflow.

Testing

• uv build
• uv build --package tangle-api
• uv run --isolated --no-project --with dist/tangle_cli-*.whl --with dist/tangle_api-*.whl python -c "import importlib.metadata as m; import tangle_cli; import tangle_api.generated.models; import tangle_api.schema; print(f'tangle-cli {m.version("tangle-cli")} with tangle-api {m.version("tangle-api")}')"
• uv publish --check-url https://pypi.org/simple/ --dry-run dist/tangle_cli-*