docs: add gitlab issue templates, code of conduct and contributing files

- update prettier config for markdown file for better readability
- fix some formatting issues

.gitlab/issue_templates/bug.md

@@ -0,0 +1,36 @@
+### Describe the bug
+
+[Summarize the bug encountered concisely]
+
+### Steps to reproduce
+
+1. [First step]
+2. [Second step]
+3. [and so on...]
+
+### Expected behavior
+
+[What you expected to happen]
+
+### Actual behavior
+
+[What actually happened]
+
+### Relevant logs and/or screenshots
+
+Paste any relevant logs - please use code blocks (```) to format console output,
+logs, and code as it's very hard to read otherwise.
+
+### Context
+
+- Castopod: [which version (or branch, if applicable) the bug is in]
+- OS: [e.g. Ubuntu server]
+- Browser: [e.g. chrome, safari]
+- Web server: [eg. Apache]
+- [any other relevant context...]
+
+### Possible fixes
+
+[If you can, link to the line of code that might be responsible for the problem]
+
+/label ~bug

.gitlab/issue_templates/feature-request.md

@@ -0,0 +1,19 @@
+### Is your feature request related to a problem? Please describe
+
+A clear and concise description of what the problem is. Ex. I'm always
+frustrated when [...]
+
+### Describe the solution you'd like
+
+A clear and concise description of what you want to happen.
+
+### Describe alternatives you've 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.
+
+/label ~feature-request