fix(python): remove CLI from wheel

[SDAChess]

Summary

The Maturin-based wheel packaging was a historical remnant from when the local gateway launch path and OpenShell CLI were coupled in one binary. The gateway and CLI now ship as standalone artifacts, so the Python distribution should contain only the SDK.

Build a single platform-independent setuptools wheel, verify that it cannot contain native code or an openshell entry point, and simplify the release jobs and documentation for SDK-only PyPI installs.

Testing

• mise run pre-commit passes
• Unit tests added/updated
• E2E tests added/updated (if applicable)

Checklist

• Follows Conventional Commits
• Commits are signed off (DCO)
• Architecture docs updated (if applicable)

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

🌿 Preview your docs: https://nvidia-preview-pr-2321.docs.buildwithfern.com/openshell

[github-actions]

Label test:e2e applied, but pull-request/2321 is at {"messa while the PR head is c8ee11d. A maintainer needs to comment /ok to test c8ee11d9d721dc17548c3d8b0958e21823621c6f to refresh the mirror. Once the mirror catches up, re-run Branch E2E Checks from the Actions tab.

[SDAChess]

/ok-to-test c8ee11d

[pimlock]

FYI there have been some openshell playbooks floating around that used the uv installation method. The one I found is already updated with the new installation method: https://build.nvidia.com/spark/openshell/instructions, so it should be good.

The uv way of installing was broken for a while anyways, since that no longer comes with a gateway, so that would already require any of these playbooks to get updated.

I think it would be worth pinging the openshell/openshell-dev channels to mention the CLI is being removed from the wheel, in case someone is still using it this way or if they have any materials that use it.

As we also mentioned before - there is no way to install the CLI only. This is useful if you have a gateway running somewhere already and just want to connect to it (e.g. gateway on remote host, connect to it from my mac). I think the consensus was to extend install script to provide this option. The uv path was the only one right now to provide managed installation of the CLI only.