Alternative:

An alternative solution found in the `wgpu` examples is:

```rust
let frame = surface
    .get_current_texture()
    .or_else(|_| {
        render_device.configure_surface(surface, &swap_chain_descriptor);
        surface.get_current_texture()
    })
    .expect("Error reconfiguring surface");
window.swap_chain_texture = Some(TextureView::from(frame));
```

See: <https://github.com/gfx-rs/wgpu/blob/94ce76391b560a66e36df1300bd684321e57511a/wgpu/examples/framework.rs#L362-L370>

The reason I went with this PR's solution is that `configure_surface`
seems to be quite an expensive operation, and it would run every frame
with the wgpu framework solution, despite the fact it works perfectly
fine without `configure_surface`.

I know this looks super hacky with the linux-specific line and the AMD
check, but my understanding is that the `Timeout` occurence is specific
to a quirk of some AMD drivers on linux, and if otherwise met should be
considered a bug.