Device lost handling

## Bevy version and features

baddb7edb7c17f8dce4f9c58380f10207c4a3cf9

## \[Optional\] Relevant system information

```ignore
SystemInfo { os: "Windows 11 Pro", kernel: "26100", cpu: "Intel(R) Core(TM) i9-14900HX", core_count: "24", memory: "127.6 GiB" }
AdapterInfo { name: "NVIDIA GeForce RTX 4090 Laptop GPU", vendor: 4318, device: 10007, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "576.52", backend: Vulkan }
```

## What you did

`cargo run --example 3d_scene`

causing a device lost by disabling the dedicated gpu in device manager

## What went wrong

There is no handling for render device migration, e.g. when switching render devices, Bevy stack overflows or panics.

## Additional information

[.log](https://github.com/user-attachments/files/22711962/default.log)

https://learn.microsoft.com/en-us/windows/uwp/gaming/handling-device-lost-scenarios

Reproduce the report with `cargo run --example 3d_scene` while disabling the dedicated GPU in Windows Device Manager, and inspect the attached `.log`. Read the linked Microsoft device-lost guidance and trace the render-device path involved in the example; done means device loss or migration no longer causes a stack overflow or panic.

Written by the indexing model from the issue text.