Add issue templates for Features/Bugs

.gitlab/issue_templates/Bug.md

+<!---
+Please read this!
+
+Before opening a new issue, make sure to search for keywords in the issues
+filtered by the "bug" label:
+
+- https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues?label_name%5B%5D=bug
+
+and verify the issue you're about to submit isn't a duplicate.
+--->
+
+### Summary
+
+(Summarize the bug encountered concisely)
+
+### Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+### What is the current *bug* behavior?
+
+(What actually happens)
+
+### What is the expected *correct* behavior?
+
+(What you should see instead)
+
+### Relevant logs and/or screenshots
+
+(Logs can be found by running `Developer: Show Logs ...` command (using `cmd+shift+p`) and selecting `Extension Host`)
+
+### Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/label ~bug ~"devops::create"  ~"group::editor" ~"Category:Editor Extension" ~"VS Code"

.gitlab/issue_templates/Feature Proposal.md

+<!---
+Please read this!
+
+Before opening a new issue, make sure to search for keywords in the issues
+filtered by the "feature" label:
+
+- https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues?label_name%5B%5D=feature
+
+and verify the issue you're about to submit isn't a duplicate.
+--->
+
+### Problem to solve
+
+<!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." -->
+
+
+### Proposal
+
+<!-- How are we going to solve the problem? -->
+
+### Further details
+
+<!-- Include examples, use cases, benefits, goals, or any other details that will help us understand the problem better. -->
+
+### Links / references
+
+/label ~feature ~"devops::create"  ~"group::editor" ~"Category:Editor Extension" ~"VS Code"