is there a good way (or any way) to have a cargo workspace where not all members have the same target? i have the (common?) use-case that i have a `no_std` library built against embedded-hal and a usage example built against a specific microcontroller (and thus specific target). the moment i have a workspace cargo seems to ignore the `.cargo/config` in the example crates.
due to the presence of tests in the library i can't run these with the target of the example crate and in other cases there might be multiple examples with different targets.

using a workspace would make it easier to just run `cargo test`, `cargo clippy`, etc. once against the root instead of having to do it for each crate separately

example repository where i'd like to use this: https://github.com/rursprung/tb6612fng-rs