Update PR and issue templates

[sairina]

Description

• More closely aligns the PR and issue templates for Studio to Kolibri's
• Splits issue template and enhancement template
• Updates the version of issue templates workflow (see warning below)

Issue Addressed (if applicable)

Addresses #2919

Comments

• If this is accepted, we will want to let the content platform circle know about the change so they're not surprised before/after the fact.
• There is still a list of reviewers, but I am sure there may be new folks we want to add to the list, if we are going to keep the list.

[indirectlylit]

I appreciate the work here! This is a hard problem and there are lots of considerations and factors so I am a big fan of making iterative changes and not blocking forward progress.

One high level consideration is that we've seen big differences between how contributors inside and outside LE learn to use our templates. Specifically, outside contributors have always struggled with complex Markdown/HTML syntax, and more generally don't follow instructions as well, and we also want to be encouraging and supportive of their attempts to help improve the products.

[indirectlylit]

thanks! couple suggestions inline.

Github issue and PR templates might be a good thing to discuss at the Dev Meeting to understand peoples' experience with the ergonomics of using them.

For example, vue.js does not use templates, but instead links to an external form for issue creation:

This sort of flow is especially helpful for external contributors who might not...

• know which git repo to post an issue in
• know how to use markdown formatting
• understand to provide all required details

[sairina]

Wow - that's fancy. Yes! I'll bring it up to the team, at the dev meeting.