Wayland error Parent device is lost

## Bevy version
bevy = { version = "0.9.0", features = ["dynamic","wayland"] }

The release number or commit hash of the version you're using.

## \[Optional\] Relevant system information
Arch Linux
cargo 1.67.0-nightly (ba607b23d 2022-11-22)

If you cannot get Bevy to build or run on your machine, please include:

- the Rust version you're using (you can get this by running `cargo --version`)
- Bevy relies on the "latest stable release" of Rust
- nightly should generally work, but there are sometimes regressions: please let us know!
> I tried with both nightly and stable versions of rust (cargo 1.65.0 (4bc8f24d3 2022-10-20))
- the operating system or browser used, including its version
- e.g. Windows 10, Ubuntu 18.04, iOS 14

If your bug is rendering-related, copy the adapter info that appears when you run Bevy.

```ignore
`AdapterInfo { name: "NVIDIA GeForce RTX 2070", vendor: 4318, device: 7938, device_type: DiscreteGpu, backend: Vulkan }`
```
thread 'main' panicked at 'Error in Surface::configure: parent device is lost', /home/aditya-yadav/.local/share/cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.0/src/backend/direct.rs:274:9

Code used -> https://pastebin.com/6ViQNHyh

You should also consider testing the examples of our upstream dependencies to help isolate any setup-specific issue:

- [`wgpu`](https://github.com/gfx-rs/wgpu) for rendering problems
- [`winit`](https://github.com/rust-windowing/winit) for input and window management
- [`gilrs`](https://docs.rs/gilrs/latest/gilrs/) for gamepad inputs

## What you did

Describe how you arrived at the problem. If you can, consider providing a code snippet or link.
I just picked the 2d_shapes example from the bevy examples site and tried to run it under wayland ( i am use KDE with wayland)
## What went wrong
The windows open fine if i disable the wayland feature but as soon as i enable it shows the above error
If it's not clear, break this out into:

- what were you expecting?
> For the same example window to open under wayland
- what actually happened?
> Nothing happen and cargo exits with the above error

## Additional information

Other information that can be used to further reproduce or isolate the problem.
This commonly includes:

- screenshots
- logs
> https://pastebin.com/4yn0H6rC
- theories about what might be going wrong
> Some drivers might working with wgpu, but i have them installed
- workarounds that you used
- links to related bugs, PRs or discussions

Start by reproducing the 2d_shapes example on KDE Wayland with Bevy 0.9.0 and the wayland feature enabled, then compare against the upstream wgpu examples mentioned in the issue. Inspect the reported panic in wgpu-0.14.0 backend/direct.rs:274 and the linked logs and code to determine whether the failure is Bevy-specific or driver/setup-specific; done means isolating the cause or documenting a confirmed fix or workaround.

Written by the indexing model from the issue text.