example panic on windows due to unimplemented in winit

## Bevy version and features
latest - 0.17.2

## \[Optional\] Relevant system information
cargo 1.90.0 (840b83a10 2025-07-30)

## What you did

git clone https://github.com/bevyengine/bevy.git
cd bevy
git checkout 0.17.2
cargo run --example breakout

## What went wrong

```
Blocking waiting for file lock on build directory
Compiling bevy v0.17.2 (D:\repo\bevy)
Finished `dev` profile [unoptimized + debuginfo] target(s) in 11m 50s
Running `target\debug\examples\breakout.exe`
2025-10-13T03:35:23.655378Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 11 Enterprise", kernel: "22635", cpu: "12th Gen Intel(R) Core(TM) i7-1260P", core_count: "12", memory: "15.7 GiB" }
2025-10-13T03:35:24.349428Z INFO bevy_render::renderer: AdapterInfo { name: "Intel(R) Iris(R) Xe Graphics", vendor: 32902, device: 18086, device_type: IntegratedGpu, driver: "Intel Corporation", driver_info: "101.6078", backend: Vulkan }
2025-10-13T03:35:25.359508Z INFO bevy_render::batching::gpu_preprocessing: GPU preprocessing is fully supported on this device.
2025-10-13T03:35:25.377415Z INFO bevy_winit::system: Creating new window breakout (0v0)

thread 'main' panicked at C:\Users\xx\.cargo\registry\src\mirrors.ustc.edu.cn-04b7754156161b43\winit-0.30.12\src\platform_impl\windows\drop_handler.rs:60:9:
not implemented
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at library\core\src\panicking.rs:225:5:
panic in a function that cannot unwind
```

Reproduce the panic by running the `breakout` example on Windows with Bevy 0.17.2. Start at winit-0.30.12's `platform_impl/windows/drop_handler.rs:60` and trace Bevy's window setup to determine the failing interaction. Done means the example starts without the `not implemented` panic on Windows.

Written by the indexing model from the issue text.