"run" and "install" subcommands

These would be useful for testing that cargo-dist builds Actually Work.

Ideally by default both would make a zip and then unpack the binary to try to best emulate end-user usage.

Similarly it would be nice if they made sure debuggers could "see" the split-debuginfo files, if at all possible.

No files, tests, or entry points are named. Start by tracing cargo-dist's current packaging and command behavior, then determine how the proposed run and install subcommands should create and unpack a zip, exercise the binary, and handle split-debuginfo files. Done means both subcommands reliably emulate end-user usage and verify debugger visibility.

Written by the indexing model from the issue text.