Update issue templates

Follow [the instructions at GitHub Documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-templates)
to recreate issue templates. Apply the new format and add new fields.

.github/ISSUE_TEMPLATE/blank_issue.md

@@ -1,5 +0,0 @@
----
-name: Blank Issue
-about: Create a blank issue.
-title: ''
----

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,41 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "Add a placeholder for issue title. ex: [BUG]"
+labels: bug
+assignees: ""
+---
+
+**Is it a security vulnerability?**
+If it results in a crash or hang, please refer to [a quick checklist](../../doc/security_need_to_know.md#is-this-bug-considered-a-security-vulnerability) to determine if it is a security vulnerability. If you are still unsure, please report it through [a security advisor](https://github.com/bytecodealliance/wasm-micro-runtime/security/advisories) and allow the maintainer to make a decision. Thank you.
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Version**
+Information like tags, release version, commits.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Compile iwasm with flags like '...'
+2. (Optional) Compile wamrc with flags like '....'
+3. (Optional) Run wamrc with CLI options like '...' to generate .aot
+4. Run iwasm with CLI options like '...'
+5. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Actual Result**
+What you've got.
+
+**Desktop (please complete the following information):**
+
+- Arch [e.g. x86_64, arm64, 32bit]
+- Board [e.g. STM32F407]
+- OS [e.g. Linux, Windows, macOS, FreeRTOS]
+- Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'Add a placeholder for issue title. ex: [RFC]'
+labels: help wanted
+assignees: ''
+
+---
+
+**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.

.github/ISSUE_TEMPLATE/improvement.md

@@ -1,28 +0,0 @@
----
-name: Improvement
-about: A feature request or code improvement.
-title: ''
-labels: ''
-assignees: ''
----
-
-Thanks for filing a feature request! Please fill out the TODOs below.
-
-#### Feature
-
-TODO: Brief description of the feature/improvement you'd like to see in WAMR
-
-#### Benefit
-
-TODO: What is the value of adding this in WAMR? What problems does it solve?
-
-#### Implementation
-
-TODO: Do you have an implementation plan, and/or ideas for data structures or
-algorithms to use?
-
-#### Alternatives
-
-TODO: What are the alternative implementation approaches or alternative ways to
-solve the problem that this feature would solve? How do these alternatives
-compare to this proposal?

.github/ISSUE_TEMPLATE/report_bug.md

@@ -1,36 +0,0 @@
----
-name: WAMR bug or defect report
-about: Report a bug or defect in WAMR
-title: ''
----
-
-Thanks for filing a bug or defect report! Please fill out the TODOs below.
-
-### Subject of the issue
-
-Describe the bug or defect here.
-
-### Test case
-
-Upload the related wasm file, wast file or the source files if you can.
-
-### Your environment
-
-* Host OS
-* WAMR version, platform, cpu architecture, running mode, etc.
-
-### Steps to reproduce
-
-Tell us how to reproduce this bug or defect.
-
-### Expected behavior
-
-Tell us what should happen
-
-### Actual behavior
-
-Tell us what happens instead
-
-### Extra Info
-
-Anything else you'd like to add?

.github/workflows/compilation_on_zephyr.yml

@@ -11,6 +11,7 @@ on:
       - synchronize
     paths:
       - ".github/**"
+      - "!.github/ISSUE_TEMPLATE/**"
       - "build-scripts/**"
       - "core/**"
       - "!core/deps/**"
@@ -27,6 +28,7 @@ on:
       - "dev/**"
     paths:
       - ".github/**"
+      - "!.github/ISSUE_TEMPLATE/**"
       - "build-scripts/**"
       - "core/**"
       - "!core/deps/**"