Verify build-std resolve against original lockfile

[adamgemmell]

What does this PR try to resolve?

Ensures that the resolve of the standard library when using build-std is a subset of the lockfile from the library source, as per discussion on rust-lang/wg-cargo-std-aware#38. It is a runtime version of the test added here: https://github.com/rust-lang/cargo/pull/13404

Fixes https://github.com/rust-lang/wg-cargo-std-aware/issues/38

How should we test and review this PR?

It can be manually tested by running cargo build -Zbuild-std --target=[host] and seeing the command succeed. I'm not sure what behaviour can exercise the negative test case.

Additional information

Co-authored-by: Lawrence Tang [email protected]

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @weihanglo (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[adamgemmell]

r? @ehuss

(nvm, I forgot a file 🙃)

[weihanglo]

@rustbot author

[bors]

:umbrella: The latest upstream changes (presumably #14358) made this pull request unmergeable. Please resolve the merge conflicts.

[weihanglo]

Close. See https://github.com/rust-lang/wg-cargo-std-aware/issues/38#issuecomment-2271758701.