Closes rust-lang#13546 (workcache: Don't assume gcc exists on all platforms)
Closes rust-lang#13545 (std: Remove pub use globs)
Closes rust-lang#13530 (test: Un-ignore smallest-hello-world.rs)
Closes rust-lang#13529 (std: Un-ignore some float tests on windows)
Closes rust-lang#13528 (green: Add a helper macro for booting libgreen)
Closes rust-lang#13526 (Remove RUST_LOG="::help" from the docs)
Closes rust-lang#13524 (dist: Make Windows installer uninstall first. Closes rust-lang#9563)
Closes rust-lang#13521 (Change AUTHORS section in the man pages)
Closes rust-lang#13519 (Update GitHub's Rust projects page.)
Closes rust-lang#13518 (mk: Change windows to install from stage2)
Closes rust-lang#13516 (liburl doc: insert missing hyphen)
Closes rust-lang#13514 (rustdoc: Better sorting criteria for searching.)
Closes rust-lang#13512 (native: Fix a race in select())
Closes rust-lang#13506 (Use the unsigned integer types for bitwise intrinsics.)
Closes rust-lang#13502 (Add a default impl for Set::is_superset)

Improved wording of or_fun_call lint

The current wording (e.g. ``use of `ok_or` followed by a function call``) is potentially confusing (at least it confused me) by suggesting that the function that follows the (in this case) `ok_or` is the problem and not the function that is an argument to it.

The code in my program that triggered the confusing message is the following:
```rust
let file_id = buf
    .lines()
    .next()
    .ok_or((
        InternalError::ProblemReadingFromInbox,
        anyhow!("No first line in inbox response ({file:?}): {buf:?}"),
    ))
    .html_context(stream, lang)?;
```
I thought that `html_context` was the problem and that I should do something along the following lines:
```rust
let file_id = buf
    .lines()
    .next()
    .ok_or_else(
        (
            InternalError::ProblemReadingFromInbox,
            anyhow!("No first line in inbox response ({file:?}): {buf:?}"),
        ),
        html_context(stream, lang),
    )?
```
This is of course wrong.  My confusion was only cleared up through the help message indicating what I should try instead.

If someone has a better idea of a replacement wording (currently e.g. ``` function call inside of `ok_or` ```), I'm all ears.

changelog: none