Add a config for the issue template chooser

[webknjaz]

This introduces a basic config for https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser. Can be adjusted later as per project needs.

[webknjaz]

Here's a few demos of how this can look in the UI:

• https://github.com/ansible/ansible/issues/new/choose
• https://github.com/pypa/pypi-support/issues/new/choose
• https://github.com/ansible/pylibssh/issues/new/choose
• https://github.com/cherrypy/cheroot/issues/new/choose
• https://github.com/sphinx-doc/sphinx/issues/new/choose

[chrahunt]

I checked on a separate repository and these end up appended to the current set of configured issue templates, which is good. 👍

[chrahunt]

I don't think the guidance for reporting PyPI/Warehouse security issues will be the same as for pip, at least because we haven't OK'd using that email distribution list for pip.

[webknjaz]

Oh, I probably copy-pasted this when merging things from a few other configs that I contributed in different projects... So this should be removed for now.

But for the future, it'd be a good idea to formalize some security issues reporting guide and put it @ https://github.com/pypa/pip/security/policy and probably re-add this section here, plus docs. In a separate PR/discussion, of course.

cc @pradyunsg ^

[webknjaz]

I checked on a separate repository and these end up appended to the current set of configured issue templates, which is good. 👍

Also, I've posted references to a few other repos where I contributed similar configs in the comments above. So people don't really have to "deploy" the thing in forks to see how it works :)

[chrahunt]

LGTM. Thank you. :)

[pradyunsg]

Me likey. :)