Relies on internals of Cargo and will break with existing / upcoming features

[epage]

term-transcript assumes the location of the production binary based on the test binary

• This isn't the case when a user sets build.build-dir (added as of Cargo 1.91)
• This isn't the case if we approve the new build-dir layout (Re-organize build-dir by package + hash, rather than artifact type rust-lang/cargo#15010)
• This isn't the case if we change the build.build-dir default (Move build-dir out of the workspace to cargo-cache-home by default rust-lang/cargo#16147)

This problem was identified by the following crater run: rust-lang/rust#149852

Ways to resolve this

• Switch to getting the bin path from a macro that is run in the caller's code, e.g. see assert_cmd::cargo::cargo_bin!
• Add a fallback using the 1.94+ runtime environment variable (feat(test): Make CARGO_BIN_EXE_ available at runtime  rust-lang/cargo#16421), e.g. assert_cmd::cargo::cargo_bin