meta: Allow blank GitHub issues

[szokeasaurusrex]

With the sub-issues beta, it appears that I am no longer able to open blank issues by manually editing the URL to https://github.com/getsentry/sentry-python/issues/new.

While users should, of course, be encouraged to use one of the templates, blank issues are often quite helpful for internal purposes. For example, in my experience with the Sentry CLI repo where blank issues are enabled, very few (perhaps none) of the issues from external users that I have triaged have been blank issues.

[antonpirker]

I am all in.

[codecov]

Test Failures Detected: Due to failing tests, we cannot provide coverage reports at this time.

❌ Failed Test Results:

Completed 13462 tests with 1 failed, 11653 passed and 1808 skipped.

View the full list of failed tests

py3.6-gevent

• Class name: tests.integrations.cloud_resource_context.test_cloud_resource_context
  Test name: test_setup_once[gcp-cloud_resource_context9-False-True]
  
  

  .../integrations/cloud_resource_context/test_cloud_resource_context.py:406: in test_setup_once
      fake_warning.assert_not_called()
  .../hostedtoolcache/Python/3.6.15.../x64/lib/python3.6/unittest/mock.py:777: in assert_not_called
      raise AssertionError(msg)
  E   AssertionError: Expected 'warning' to not have been called. Called 2 times.

[sentrivana]

Sure why not.