templates: use a new bug template based on forms.

Use a form based template instead of freesyle template. This will force
bug reporters to follow the template and provide the needed information
and will make triage easier and bug reports consistent.

Signed-off-by: Anas Nashif <[email protected]>

Author: nashif

.github/ISSUE_TEMPLATE/001_bug_report.md

@@ -0,0 +1,82 @@
+name: Bug Report
+description: File a bug report.
+labels: ["bug"]
+type: "Bug"
+projects: ["octo-org/1", "octo-org/44"]
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Describe the bug
+      description: |
+        A clear and concise description of what the bug is.
+
+      placeholder: |
+        Please also mention any information which could help others to understand
+        the problem you're facing:
+          - What target platform are you using?
+          - What have you tried to diagnose or workaround this issue?
+          - Is this a regression? If yes, have you been able to "git bisect" it to a
+            specific commit?
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: |
+        Steps to reproduce the behavior.
+
+      placeholder: |
+        Steps to reproduce the behavior:
+          1. mkdir build; cd build
+          2. cmake -DBOARD=board\_xyz
+          3. make
+          4. See error
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: dropdown
+    attributes:
+      label: Impact
+      description: Impact of this bug
+      multiple: false
+      options:
+        - Showstopper – Prevents release or major functionality; system unusable.
+        - Major – Severely degrades functionality; workaround is difficult or unavailable.
+        - Functional Limitation – Some features not working as expected, but system usable.
+        - Annoyance – Minor irritation; no significant impact on usability or functionality.
+        - Intermittent – Occurs occasionally; hard to reproduce.
+        - Not sure
+      default: 3
+    validations:
+      required: true
+  - type: textarea
+    id: env
+    attributes:
+      label: Environment
+      description: please complete the following information
+      placeholder: |
+       - OS: (e.g. Linux, MacOS, Windows)
+       - Toolchain (e.g Zephyr SDK, ...)
+       - Commit SHA or Version used
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: |
+        By submitting this issue, you agree to follow our
+        [Code of Conduct](https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md).
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/001_bug_report.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Zephyr Community Support
+    url: https://github.com/zephyrproject-rtos/zephyr/discussions
+    about: Please ask and answer questions here.