Remove uses of cfg({any()/all()})

[clubby789]

This implements the followup warning suggested in rust-lang/rfcs#3695
Lint against an empty cfg(any/all), suggest the boolean literal equivalents.
#149791 (comment)

Tracking issue: #131204

[rustbot]

Some changes occurred in check-cfg diagnostics

cc @Urgau

Some changes occurred in compiler/rustc_attr_parsing

cc @jdonszelmann

[rustbot]

r? @chenyukang

rustbot has assigned @chenyukang.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[jdonszelmann]

r? jdonszelmann

[Urgau]

Can you split-off the FALSE -> false suggestion into it's own PR?

As for the warning it should probably be a lint (so it can be enabled and disabled), but either way the warning will need to go through T-lang first, with a nomination and maybe a crater run.

[joshtriplett]

With my T-lang hat on, this seems reasonable. Nominating for discussion of the new lint.

[clubby789]

Running into the above error where

    (@__items ($($not:meta,)*) ; ( ($($m:meta),*) ($($tokens:tt)*) ), $($rest:tt)*) => {
        #[cfg(all($($m,)* not(any($($not),*))))] cfg_if! { @__identity $($tokens)* }
        cfg_if! { @__items ($($not,)* $($m,)*) ; $($rest)* }
    };

is invoked with no $not, meaning we expand to not(any()) and raise the lint. Inclined to think that we should only lint for the literal any()/all() cases instead

[rustbot]

This PR modifies tests/ui/issues/. If this PR is adding new tests to tests/ui/issues/,
please refrain from doing so, and instead add it to more descriptive subdirectories.

Some changes occurred in src/tools/clippy

cc @rust-lang/clippy

[clubby789]

Implemented as a pre-expansion early lint

[jdonszelmann]

Though I'm not T-lang, I agree with josh that this is a good lint to add. Just got some comments about the implementation but nothing too major. Just gotta clean some things up :)

View changes since this review