`cargo component check --workspace` should not generate bindings for workspace members without `[package.metadata.component]` set

I have a workspace that has some components within it so I am using `cargo component check --workspace` to check that all of the workspace members are working. However, one workspace member is a host and not a guest program. This means it has a `wit` directory but cargo-component should still treat it as a normal Rust binary and not attempt to generate binaries. Presumably if `[package.metadata.component]` is not set in the Cargo.toml manifest, then it should be safe to assume that the crate is not meant to be compiled as a component using cargo-component.