Allow tangle-cli releases with independent tangle-api version

[Volv-G]

Summary

• relax the release smoke tests so tangle-cli and tangle-api do not need identical distribution versions
• keep import smoke coverage for tangle_cli, tangle_api.generated.models, and tangle_api.schema
• publish with uv publish --check-url https://pypi.org/simple/ so unchanged distributions such as tangle-api==0.1.0 are skipped instead of re-uploaded

Context

tangle-cli 0.1.1 is a CLI-only patch and intentionally depends on the existing tangle-api==0.1.0. The current release workflow assumes the two packages always rev in lockstep, which blocked publishing tangle-cli 0.1.1 even though the package metadata is valid.

After this lands, I will retag v0.1.1 at the fixed master commit to re-run the PyPI 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/*