path / private info sanitization?

I vaguely recall there's a cargo/rustc flag for stripping build-machine paths from the binary or something. Not terribly important for CI builds, but important if anyone opts to use this manually. Good Defaults!

No files, tests, or entry points are named. Research the cargo/rustc option for stripping build-machine paths, then trace how cargo-dist handles manually used builds and release artifacts. Done means the relevant default prevents private build paths from being embedded without disrupting CI packaging.

Written by the indexing model from the issue text.