Short IDs don't resolve for runner-hosted sandboxes in `logs sandbox` and `sandbox exec`

sandbox exec, logs sandbox, and deploy cancel fail to resolve short IDs when targeting entities on distributed runners (or generally when the short ID doesn't match the full entity ID).

For exec, the short ID gets sent to the runner which tries to match it against containerd container names and fails. For logs sandbox, the short ID silently returns no results. For deploy cancel, the short ID is passed to EAC.Get() which expects a full entity ID, so the cancel reports success but never actually updates the deployment entity, leaving the deploy lock stuck until it expires (30 min timeout).

The deploy cancel case is particularly nasty because the lock info message displays the short ID (Deployment ID: 3sA), and deploy cancel -d 3sA is the obvious thing to type. It says "Cancelled deployment 3sA" but the lock persists. Found this during MIR-965 validation on Toys.

Worth doing a sweep for all commands that accept entity IDs as arguments to make sure they all resolve short IDs consistently.