chore: Add Github Issue templates & webui sysinfo (#681)

* chore: better gh templates

* chore: add about - sysinfo to gh issues

* fix: Webui freeze on auth error

* Split Git Remote to own field

* Move CONTRIBUTING.md

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Create a report to help us improving Hyperion
+
+---
+
+<!-- Please don't delete this template or we'll close your issue -->
+<!-- Before creating an issue please make sure you are using the latest version of Hyperion. -->
+
+<!-- Please confirm you will submit an issue. -->
+<!-- Issues which contain questions or support requests will be closed. -->
+<!-- (Update "[ ]" to "[x]" to check a box) -->
+
+- [x] I confirm that this is an issue rather than a question.
+
+<!-- Please ask questions here -->
+<!-- https://hyperion-project.org -->
+
+## Bug report
+
+
+#### Steps to reproduce
+
+
+#### What is expected?
+
+
+#### What is actually happening?
+
+
+#### System
+<!-- Your system information - please copy paste "System info (Github Issue)" section from web configuration/system/about -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for Hyperion
+
+---
+
+<!-- Please don't delete this template or we'll close your issue -->
+<!-- Before creating an issue please make sure you are using the latest version of Hyperion. -->
+
+## Feature request
+
+<!-- Please ask questions on our Forum. -->
+<!-- https://hyperion-project.org -->
+<!-- Issues which contain questions or support requests will be closed. -->
+
+#### What problem does this feature solve?
+
+#### What does the proposed API look like?
+
+#### How should this be implemented in your opinion?
+
+#### Are you willing to work on this yourself?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,39 @@
+<!-- Please don't delete this template -->
+
+<!-- PULL REQUEST TEMPLATE -->
+<!-- (Update "[ ]" to "[x]" to check a box) -->
+
+**Summary**
+
+**What kind of change does this PR introduce?** (check at least one)
+
+- [ ] Bugfix
+- [ ] Feature
+- [ ] Code style update
+- [ ] Refactor
+- [ ] Docs
+- [ ] Build-related changes
+- [ ] Other, please describe:
+
+If changing the UI of web configuration, please provide the **before/after** screenshot:
+
+**Does this PR introduce a breaking change?** (check one)
+
+- [ ] Yes
+- [ ] No
+
+If yes, please describe the impact and migration path for existing setups:
+
+**The PR fulfills these requirements:**
+
+- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
+
+If adding a **new feature**, the PR's description includes:
+
+- [ ] A convincing reason for adding this feature
+- [ ] Related documents have been updated (docs/docs/en)
+- [ ] Related tests have been updated
+
+To avoid wasting your time, it's best to open a **feature request issue** first and wait for approval before working on it.
+
+**Other information:**