Make the reproducer mandatory in the issue template

Summary:
As the title says, let's make this field mandatory so we don't have to ask for
a repro over and over again.

Changelog:
[Internal] [Changed] - Make the reproducer mandatory in the issue template

Reviewed By: cipolleschi

Differential Revision: D36552021

fbshipit-source-id: ac6aa0c3b1583afe38b3fcf78c385e5bdfb5f6e2

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -43,5 +43,6 @@ body:
         Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
         You may provide a screenshot of the application if you think it is relevant to your bug report.
         Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
+        Please note that a reproducer is mandatory. Issues without reproducer are more likely to stall and will be closed.
     validations:
-      required: false
+      required: true

.github/ISSUE_TEMPLATE/new_architecture_bug_report.yml

@@ -48,5 +48,6 @@ body:
         Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
         You may provide a screenshot of the application if you think it is relevant to your bug report.
         Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
+        Please note that a reproducer is mandatory. Issues without reproducer are more likely to stall and will be closed.
     validations:
-      required: false
+      required: true