Get more structured data for new Github issues by using Issue Templates

[petrhollayms]

We need to improve the quality of new GitHub issues from our users in order to be quickly assess the impact and urgency and assign the priority correctly, without multiple iterations with our users on clarifying the issue (e.g., to understand how to reproduce the bug).

One way for doing this is to create structured forms for new issues in GitHub, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Acceptance Criteria

• Agree with Kiota team which fields to collect for bug reports and new feature requests
• Review the initial proposal and compare which fields from .NET team we can/shall be using: https://microsofteur-my.sharepoint.com/:w:/g/personal/shemogumbe_microsoft_com/EWAFHtN2jltNnqA1wWoW3PEBBNBEW7oAyoJitcSsU47_ig?e=3DnUGj
• User can create a new bug report or feature request using a new issue template
• Forms contain fields for all important information we want to collect
• Option for creating a "blank issue" shall remain available.
• New issue templates are being reviewed with @andrueastman and @sebastienlevert before enabling them in Kiota repo for our users.
• Use it for Kiota and/or C# SDK first, get some feedback before rolling it out to the remaining repos.

We want to build on the initial work done by @calebkiage here.

For inspiration, see the issue templates used by .NET Core team: https://github.com/dotnet/runtime/tree/main/.github/ISSUE_TEMPLATE

[petrhollayms]

Adding the first proposal from @fey101 for the reference: https://github.com/microsoftgraph/msgraph-issue-templating/issues/new/choose

[baywet]

Roughly in agreement with what's being proposed here, I'd make a couple of tweaks to the bug report template when we deploy it to language repositories:

• remove "What are you generating using Kiota, clients or plugins?"
• remove "In what context or format are you using Kiota?"
• remove "Client Library/SDK Language"
• add a "library version" field
• make "Open API description file" optional

[baywet]

We should also probably decide on whether we keep GitHub discussions on, and what do we do with things that are "questions"?

[fey101]

Initial design and samples already in use. Created a ticket to collect feedback and roll out the templates to remaining repos.