`cargo clippy -- --target wasm32-unknown-unknown` results in confusing failures.

Description

Running cargo clippy -- --target wasm32-unknown-unknown will give strange failures, while cargo clippy --target wasm32-unknown-unknown will succeed as expected.
The failure occurs for any crate containing dependencies, for example I reproduced it with a minimal crate just pulling in and using anyhow.

I assume that the 2nd command is the correct way to use clippy while the 1st command is passing --target to some internal part of clippy which shouldnt really be exposed to the user.
However this is quite confusing behavior for the user.

Instead, at the very least, clippy should detect when --target is passed after -- and give the user a useful error, directing them to put it before the -- instead.
But maybe a more general solution is possible, I'm not familiar with the internals here.

Version

rustc 1.77.0 (aedd173a2 2024-03-17)
binary: rustc
commit-hash: aedd173a2c086e558c2b66d3743b344f977621a7
commit-date: 2024-03-17
host: x86_64-unknown-linux-gnu
release: 1.77.0
LLVM version: 17.0.6

Additional Labels

No response

Reproduce the behavior with a minimal Rust crate that depends on anyhow, comparing cargo clippy -- --target wasm32-unknown-unknown with cargo clippy --target wasm32-unknown-unknown. Start by tracing how Clippy and Cargo handle arguments after --; done means the misplaced target argument is rejected with a useful message or otherwise no longer causes confusing dependency failures.