Add ./x clippy ci

[emilyalbini]

The mingw-check job runs some Clippy lints with custom -D and -A flags, and that is annoying when trying to reproduce that behavior locally. The only way to reproduce what CI is doing today is to go look at the dockerfile for that job, and that is far from ideal.

This came up when doing the stage0 bump to 1.80.0 (#126273), as during stage0 bumps we get the new Clippy lints for the release. We don't want to update the release process instructions every single time something changes in the CI configuration, but rather I'd like a single command I can put in the instructions to check for newly introduced Clippy lints.

This PR adds that: the new ./x clippy ci does what we do today in our CI, and the PR switches the mingw-check job to run that command.

[rustbot]

r? @onur-ozkan

rustbot has assigned @onur-ozkan.
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

[rust-log-analyzer]

The job x86_64-gnu-llvm-17 failed! Check out the build log: (web) (plain)

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

#17 exporting to docker image format
#17 sending tarball 31.3s done
#17 DONE 36.2s
##[endgroup]
Setting extra environment values for docker:  --env ENABLE_GCC_CODEGEN=1 --env GCC_EXEC_PREFIX=/usr/lib/gcc/
[CI_JOB_NAME=x86_64-gnu-llvm-17]
---
sccache: Starting the server...
##[group]Configure the build
configure: processing command line
configure: 
configure: build.configure-args := ['--build=x86_64-unknown-linux-gnu', '--llvm-root=/usr/lib/llvm-17', '--enable-llvm-link-shared', '--set', 'rust.thin-lto-import-instr-limit=10', '--set', 'change-id=99999999', '--enable-verbose-configure', '--enable-sccache', '--disable-manage-submodules', '--enable-locked-deps', '--enable-cargo-native-static', '--set', 'rust.codegen-units-std=1', '--set', 'dist.compression-profile=balanced', '--dist-compression-formats=xz', '--disable-dist-src', '--release-channel=nightly', '--enable-debug-assertions', '--enable-overflow-checks', '--enable-llvm-assertions', '--set', 'rust.verify-llvm-ir', '--set', 'rust.codegen-backends=llvm,cranelift,gcc', '--set', 'llvm.static-libstdcpp', '--enable-new-symbol-mangling']
configure: target.x86_64-unknown-linux-gnu.llvm-config := /usr/lib/llvm-17/bin/llvm-config
configure: llvm.link-shared     := True
configure: rust.thin-lto-import-instr-limit := 10
configure: change-id            := 99999999
---
  Downloaded boml v0.3.1
   Compiling boml v0.3.1
   Compiling y v0.1.0 (/checkout/compiler/rustc_codegen_gcc/build_system)
    Finished `release` profile [optimized] target(s) in 3.57s
     Running `/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-codegen/x86_64-unknown-linux-gnu/release/y test --use-system-gcc --use-backend gcc --out-dir /checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/cg_gcc --release --mini-tests --std-tests`
Using system GCC
[BUILD] example
[AOT] mini_core_hello_world
/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-tools/cg_gcc/mini_core_hello_world
abc
---
   |
note: the function `get_clippy_rules_in_order` is defined here
  --> src/core/build_steps/clippy.rs:84:1
   |
84 | fn get_clippy_rules_in_order(all_args: &[String], config: &LintConfig) -> Vec<String> {

For more information about this error, try `rustc --explain E0603`.
error: could not compile `bootstrap` (lib test) due to 1 previous error
Build completed unsuccessfully in 0:37:37

[bors]

☔ The latest upstream changes (presumably #128334) made this pull request unmergeable. Please resolve the merge conflicts.

[alex-semenyuk]

@pietroalbini
Ping from triage. Could you please post your status on this PR? This PR has not received an update for a few months.
It has merge conflicts and failed CI