Switching to new Issue GitHub's form schema

[abhiTronix]

Brief Description

GitHub's form schema that uses YAML instead of markdown is currently in beta. These new YAML Issue GitHub's form schema have a lot of major benefits that this repository could benefit from which are discussed in #319 (comment)

Requirements / Checklist

• I have read the PR Guidelines.
• I have read the Documentation.
• I have updated the documentation accordingly(if required).

Related Issue

#319

Context

GitHub's form schema for those who don't know are essentially enhanced Issue templates, allowing more freedom in designing issue templates. There is a page providing some info about the new GitHub's form schema issue forms: https://gh-community.github.io/issue-template-feedback/structured/. Thereby this PR will replace traditional Markdown Issue forms with new Issue GitHub's form schema.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Screenshots (if available):

[codecov]

Codecov Report

Merging #320 (357e9c7) into testing (98a1662) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           testing     #320   +/-   ##
========================================
  Coverage    95.05%   95.05%           
========================================
  Files           16       16           
  Lines         3074     3074           
========================================
  Hits          2922     2922           
  Misses         152      152           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 98a1662...357e9c7. Read the comment docs.