Feature Request: Detect `no_std` per-crate and ignore `check.allTargets`

If possible, the option for RA to detect that a crate* is no_std and disable check.allTargets, to seamlessly prevent issues like #2142 once and for all, where you can either have RA checking tests where it makes sense, or you can stop bogus errors in no_std crates, but not both.

*specifically, in my case, I have a VSCode workspace with various cargo crates/workspaces, some no_std, some not, with per-folder .cargo/config.toml setting targets.

Alternatively, another option would be do detect no_std and use a new option, checkOnSave.extraNoStdArgs, for something like as a (manual) solution. Or both?

{
    "rust-analyzer.checkOnSave.allTargets": false,
	"rust-analyzer.checkOnSave.extraArgs": [
        "--all-targets"
    ]
    "rust-analyzer.checkOnSave.extraNoStdArgs": [
        "--bins"
    ]
}

No files, tests, or entry points are named in the issue. Start by reviewing rust-analyzer's check-on-save settings and the proposed per-crate no_std detection, then clarify whether automatic check.allTargets handling, extraNoStdArgs, or both are required. Done means behavior is defined for mixed workspaces with per-folder .cargo/config.toml target settings.