rename cargo-dist

cargo-dist has aspirations to be not-just-cargo, so it should... not be called cargo-dist. probably for rust users it will continue to be available as "cargo dist", but i don't want to tell anyone to use `cargo-dist dist init` when using it with not-cargo.

An Eternal Question / Meme here at axodotdev is: surely we should have a tool called "axo" that does all the things. As cargo-dist has increasingly become a bigger tent (especially if we do #842), it's increasingly looking like the fabled "axo". Or maybe it's "axo dist" (axo-dist).

The cargo subcommand trick is cute, but also a bit of a logistical nightmare for not-cargo to do, so if we do want to be invoked as "axo dist", that realistically means an axo monorepo with cargo-dist just being part of the workspace. If we do "axo dist" then maybe #842 is "axo release", instead of what may have presumably become "axo dist release"?

Review the proposed names, including "axo" and "axo-dist", alongside the implications for the cargo subcommand and the possible #842 work. The issue is done only after the project agrees on a name and defines the migration scope; no files or tests are identified here.

Written by the indexing model from the issue text.