More clarity around bug reports

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -14,6 +14,10 @@ body:
         - Search the issue tracker using [this link](https://github.com/wailsapp/wails/issues?q=is%3Aissue+).
         - Search the [discussion forums](https://github.com/wailsapp/wails/discussions?discussions_q=type+your+issue+here).
         - Read the [Troubleshooting Guide](https://wails.io/docs/next/guides/troubleshooting).
+        - Create a [Minimal Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example) and link to it in the issue.
+        - If your issue is related to TypeScript generation, please open a ticket and create a PR with a failing test case.
+        TS tests can be found [here](https://github.com/wailsapp/wails/tree/master/v2/internal/binding/binding_test). Remember to add
+        your test to the `binding_test.go` file.
         - Try to fix it yourself. Keep a list of things you have done to fix the problem.   
 
         If after doing all the above, the problem remains, please continue with this ticket providing *all* the information requested.

website/src/pages/community-guide.mdx

@@ -82,6 +82,7 @@ The process for fixing bugs are as follows:
 - The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to
   prove that it is a Wails issue with a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example)
 - The output of `wails doctor`
+- A test that can reproduce the bug
 - If the ticket does not include this information, feel free to request the information from the
   person who opened the ticket.
 - Comment on the ticket stating you wish to develop a fix