chore: update issue templates (#1105)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Report any bugs or unexpected behavior
+title: 'bug: '
+labels: bug, track:maintenance
+assignees: ''
+
+---
+
+### Problem
+A clear and concise description of what the bug is.
+
+### Impact
+Indicate how significant you believe the impact of the bug is. Bugs that lead to data loss or corruption would be considered `critical`. In such cases, please also add the `critical` label.
+
+### To reproduce
+If you can reproduce the behavior, steps to reproduce:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+### Expected behavior
+A clear and concise description of what you expected to happen.
+
+### Screenshots/logs
+If applicable, add screenshots or logs to help explain your problem.
+
+### nwaku version/commit hash
+State the version of `nwaku` where you've encountered the bug or, if built off a specific commit, the relevant commit hash. You can check the version by running `./wakunode2 --version`.
+- e.g. `v0.9` or `ed53bcd`
+
+### Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for the nwaku implementation
+title: 'feat: '
+labels: track:production
+assignees: ''
+
+---
+
+### Problem
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+### Suggested solution
+A clear and concise description of what you want to happen.
+
+### Alternatives considered
+A clear and concise description of any alternative solutions or features you've considered.
+
+### Additional context
+Add any other context or screenshots about the feature request here.
+
+### Acceptance criteria
+A list of tasks that need to be done for the issue to be considered resolved.

.github/ISSUE_TEMPLATE/improvement.md

@@ -0,0 +1,17 @@
+---
+name: Improvement
+about: Suggest improvements to the codebase or processes. This includes refactoring,
+  docs and any other chores.
+title: 'chore:'
+labels: track:maintenance
+assignees: ''
+
+---
+### Background
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]; There is a spelling error in [...]; It's difficult to read the code in module [...]
+
+### Details
+A clear and concise description of what you want to happen.
+
+### Acceptance criteria
+A list of tasks that need to be done for the issue to be considered resolved.

.github/ISSUE_TEMPLATE/research-related-issue.md

@@ -0,0 +1,19 @@
+---
+name: Research-related issue
+about: Use this template if your issue is related to any Vac research tracks
+title: 'research:'
+labels: ''
+assignees: ''
+
+---
+
+### Problem
+
+### Acceptance criteria
+
+### Details
+
+### Possible Solutions
+
+### Research track
+Indicate the Vac research track that this issue relates to. Please also add the relevant track as a label.