Make bug template more beginner-friendly (#4652)

# Objective

1. "What you expected to happen" and "what actually happened" often involves trivial duplication.
2. "Please provide full reproduction steps" is not helpful advice to new contributors.
3. The OS field was commonly useless or inadequate.
4. The description for "additional information" effectively just repeated the title of the field.

## Solution

1. Unify these fields into a single "what went wrong" field.
2. Provide an example of a useful reproduction.
3. Replace OS field with an optional "Setup Information" field that captures information about other critical setup like Rust version and hardware.
4. Provide helpful advice about what sort of information may be useful to add.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -10,23 +10,46 @@ assignees: ''
 
 The release number or commit hash of the version you're using.
 
-## Operating system & version
+## \[Optional\] Relevant system information
 
-Ex: Windows 10, Ubuntu 18.04, iOS 14.
+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!
+- 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 }`
+```
+
+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
 
-The steps you took to uncover this bug. Please list full reproduction steps if
-feasible.
+Describe how you arrived at the problem. If you can, consider providing a code snippet or link.
 
-## What you expected to happen
+## What went wrong
 
-What you think should've happened if everything was working properly.
+If it's not clear, break this out into:
 
-## What actually happened
-
-The actual result of the actions you described.
+- what were you expecting?
+- what actually happened?
 
 ## Additional information
 
-Any additional information you would like to add such as screenshots, logs, etc.
+Other information that can be used to further reproduce or isolate the problem.
+This commonly includes:
+
+- screenshots
+- logs
+- theories about what might be going wrong
+- workarounds that you used
+- links to related bugs, PRs or discussions