Decouple test and proc_macro

[Zoxc]

This decouples the test and proc_macro crates by having bootstrap build both at the same time instead of having proc_macro be a dependency of test. This allows them to build in parallel saving around 9 seconds locally.

The std is also built directly by bootstrap avoiding the extra features on the test crate.

This is an alternative to #108865.

[rustbot]

r? @albertlarsan68

(rustbot has picked a reviewer for you, use r? to override)

[rustbot]

These commits modify the Cargo.lock file. Random changes to Cargo.lock can be introduced when switching branches and rebasing PRs.
This was probably unintentional and should be reverted before this PR is merged.

If this was intentional then you can ignore this comment.

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with @rustbot label +T-libs-api -T-libs to tag it appropriately. If this PR contains changes to any unstable APIs please edit the PR description to add a link to the relevant API Change Proposal or create one if you haven't already. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

• Stabilizing library features
• Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
• Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
• Changing public documentation in ways that create new stability guarantees
• Changing observable runtime behavior of library APIs

[rustbot]

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with @rustbot label +T-libs-api -T-libs to tag it appropriately. If this PR contains changes to any unstable APIs please edit the PR description to add a link to the relevant API Change Proposal or create one if you haven't already. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

• Stabilizing library features
• Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
• Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
• Changing public documentation in ways that create new stability guarantees
• Changing observable runtime behavior of library APIs

These commits modify the Cargo.lock file. Random changes to Cargo.lock can be introduced when switching branches and rebasing PRs.
This was probably unintentional and should be reverted before this PR is merged.

If this was intentional then you can ignore this comment.

[rust-log-analyzer]

The job mingw-check failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[Zoxc]

@jyn514 You'll want to look at the error on the first commit. The second is my attempted fix.

[jyn514]

error: the argument '--package [<SPEC>]' cannot be used multiple times

@Zoxc you can use RUSTDOCFLAGS=... cargo doc instead of cargo rustdoc ....

[Zoxc]

I'll have to remove the ability to document individual crates then, as different crates may have different sets of features.

[jyn514]

I think it would be possible to change which --features we pass to cargo depending on the specific crate being documented. But I agree at that point it's getting quite complicated. I don't have strong opinions on whether to land this or #108865.

[Zoxc]

I'm going to favor #108865 then as I'd prefer not to reimplement cargo features in bootstrap. Ideally cargo would have to ability to specify features for a whole workspace here.