Create issue template for new kafka topic requests

[theferrit32]

Information to provide in topic requests:

• Topic name
• Number of partitions (strongly suggest limiting to 1 partition)
• Do messages need to be persistent? (two options: infinite retention, 1 week retention)
• Who is the producer developer contact for this topic?
  • What API key name should be granted write access?
• Who is the intended consumer of this topic?
• Which cluster(s) should it be created on (staging or production)?
  • For in-development applications, start with just a single topic on staging cluster. When production ready, create it on production, potentially deleting the staging one until needed later.
• Is there information that is sensitive or not desirable to be shared publicly?
  • All topics have read access restricted to authenticated users and a specific set of service accounts. This question is just for making a note that granting additional permissions needs to be stricter as well.

[sjahl]

If you click the New Issue button over at https://github.com/clingen-data-model/data-exchange-topics/issues, you'll see the option to use the new topic form. The source is at https://github.com/clingen-data-model/data-exchange-topics/blob/main/.github/ISSUE_TEMPLATE/new_topic_request.yaml

GIthub forms are still in beta, but they seem to be working reasonably well so far. Docs are at: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms