Bug report template is hard to use

[designsimply]

A report has come in that the bug report template is hard to use.

Goal: make bug reporting as easy as we can while still getting as much basic and helpful information as possible up front.

Why we want to simplify:

• Bug reports should be easy to submit.
• You can always ask questions for clarification later if needed.
• The WP apps bug report template has been working pretty well!

Current Woo bug report template:

**Describe the bug**
A clear and concise description of what the bug is. Please be as descriptive as possible; issues lacking detail, or for any other reason than to report a bug, may be closed without action.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Expected behavior**
A clear and concise description of what you expected to happen.

**Isolating the problem (mark completed items with an [x]):**
- [ ] I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
- [ ] This bug happens with a default WordPress theme active, or [Storefront](https://woocommerce.com/storefront/).
- [ ] I can reproduce this bug consistently using the steps above.

**Mobile Environment**
Please include:
- Device: 
- iOS version: 
- WooCommerce iOS version: 

**WordPress Environment**
<details>
Copy and paste the system status report from **WooCommerce > System Status** in WordPress admin.
</details>

Suggested change is to align better with the WordPress apps bug template which looks like this:

### Expected behavior

### Actual behavior

### Steps to reproduce the behavior

##### Tested on [device], iOS [version], WPiOS [version]

^{(internal reference: p77Llu-dvG-p2 @aerych)}

[shiki]

Based on the discussion in #1944, the consensus seems to be to keep the template as is. I'll close this, for now, to keep the backlog clean but we can always reopen it in the future.