The docs for `.cargo/config.toml` mention that:
> At present, when being invoked from a workspace, Cargo does not read config files from crates within the workspace. i.e. if a workspace has two crates in it, named /projects/foo/bar/baz/mylib and /projects/foo/bar/baz/mybin, and there are Cargo configs at /projects/foo/bar/baz/mylib/.cargo/config.toml and /projects/foo/bar/baz/mybin/.cargo/config.toml, Cargo does not read those configuration files if it is invoked from the workspace root (/projects/foo/bar/baz/).

How do you propose I deal with this issue, where a workspace has crates that are intended to be built for `aarch64-unknown-linux-gnu` but some specific ones can be (local) macos/windows/linux?