Rollup of 8 pull requests

[Centril]

Successful merges:

• Add test for #43398 #62994 (Add test for ICE getting discriminant of #[repr(i128)] enum #43398)
• Add tests for some issues #63259 (Add tests for some issues)
• bump rand in libcore/liballoc test suites #63261 (bump rand in libcore/liballoc test suites)
• doc: Reword deprecation message of MetadataExt::as_raw_stat #63327 (doc: Reword deprecation message of MetadataExt::as_raw_stat)
• Test conditional initialization validation in async fns #63331 (Test conditional initialization validation in async fns)
• Update to rustc-guide that passes toolstate #63334 (Update to rustc-guide that passes toolstate)
• Update books #63353 (Update books)
• Use consistent capitalization in -C/-Z help #63360 (Use consistent capitalization in -C/-Z help)

Failed merges:

r? @ghost

[Centril]

@bors r+ p=8 rollup=never

[bors]

📌 Commit ed36ead has been approved by Centril

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout rollup-kl5w1p2 (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self rollup-kl5w1p2 --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

warning: Cannot merge binary files: Cargo.lock (HEAD vs. heads/homu-tmp)
Auto-merging Cargo.lock
CONFLICT (content): Merge conflict in Cargo.lock
Automatic merge failed; fix conflicts and then commit the result.