cargo clippy failure for crate level UMDF config

Seems like running cargo build --all-features does not play nicely with the UMDF config uncommented in the root cargo.toml. Somehow, the DRIVER_OBJECT is not able to be detected in root. After investigation, this type is generated in the bindings.

A clean cargo build builds perfectly fine.

error[E0432]: unresolved import `crate::DRIVER_OBJECT`
  --> crates\wdk-sys\src\test_stubs.rs:18:13
   |
18 | use crate::{DRIVER_OBJECT, NTSTATUS, PCUNICODE_STRING};
   |             ^^^^^^^^^^^^^
   |             |
   |             no `DRIVER_OBJECT` in the root
   |             help: a similar name exists in the module: `PDRIVER_OBJECT`

For more information about this error, try `rustc --explain E0432`.
error: could not compile `wdk-sys` (lib) due to 1 previous error

Reproduce the failure with cargo build --all-features, then compare it with a clean cargo build. Start with the UMDF configuration in the root cargo.toml, crates/wdk-sys/src/test_stubs.rs, and the generated bindings; done means the all-features build no longer reports the missing DRIVER_OBJECT import.