chore(github): update issue templates

* .github/ISSUE_TEMPLATE/config.yml: replaced the previous link that was
  pointing to the "eclipse-zenoh" organisation with a link to the
  Discord server.
* .github/ISSUE_TEMPLATE/enhancement.yml: new template to suggest
  enhancement to Zenoh-Flow.

Signed-off-by: Julien Loudet <[email protected]>

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Ask a question
-    url: https://github.com/eclipse-zenoh/roadmap/discussions/categories/zenoh-flow
-    about: Open to the Zenoh Flow community. Share your feedback with the Zenoh Flow team.
+  - name: Talk with us!
+    url: https://discord.gg/WsUF9GSkUJ
+    about: The Zenoh and Zenoh-Flow Discord server.

.github/ISSUE_TEMPLATE/enhancement.yml

@@ -0,0 +1,36 @@
+name: Enhancement
+
+description: |
+  How the API or internal structure of Zenoh-Flow can be improved.
+
+title: "[Enhancement] "
+
+labels: ["enhancement"]
+
+body:
+  - type: textarea
+    id: current
+    attributes:
+      label: "Current behaviour and limitations"
+      description: |
+        A description of the current state / behaviour of Zenoh-Flow and how it
+        is limiting.
+      placeholder: |
+        E.g. A node does not have access to the path of its implementation on
+        the device running it. This is limiting for the bindings as for some
+        languages this information is required (i.e. Python with PyO3).
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: "Proposed solution?"
+      description: |
+        A description of a possible solution that would help address the
+        limitation(s) described above.
+      placeholder: |
+        E.g. The path of the implementation of a node can be passed in the
+        `Context` structure.
+    validations:
+      required: false