feat(storage): validate engine-device compatibility statically

Summary

• preserve concrete device types through DeviceBuilder and validate engine-device pairs before type erasure
• add the extensible DeviceFor marker trait, a centralized BlockEngine compatibility list, and targeted compiler diagnostics
• expose concrete device and partition types needed by downstream implementations
• move runtime device selection in foyer-bench after static engine-config construction
• add compile-pass and compile-fail coverage for built-in pairs and downstream extension paths
• keep compile-time UI tests isolated from the madsim runtime feature set
• align the local cargo x license step with CI's HawkEye configuration

API compatibility

• DeviceBuilder now declares an associated Device type and returns Arc<Self::Device>
• BlockEngineConfig::new requires the concrete device type to implement DeviceFor<Self>
• callers that erase a device to Arc<dyn Device> before engine construction must delay erasure or erase the completed EngineConfig instead

Testing

• cargo x --fast
• RUSTFLAGS='--cfg tokio_unstable --cfg madsim' cargo nextest run --workspace --exclude foyer-bench --exclude examples --no-default-features --features 'runtime-madsim-tokio'