converting feature and test templates from md to yml

[MistzSoftware]

Description

This pull request includes updates to the issue templates in the .github/ISSUE_TEMPLATE directory. The primary changes involve converting markdown-based templates to YAML-based templates for better structure and validation.

Conversion to YAML-based templates:

• .github/ISSUE_TEMPLATE/bug-report.yml: Added projects and type fields to the bug report template.

• .github/ISSUE_TEMPLATE/feature-request.md: Removed the markdown-based feature request template.

• .github/ISSUE_TEMPLATE/feature-request.yml: Created a new YAML-based feature request template with structured fields for description, motivation, solution, alternatives, and additional context.

• .github/ISSUE_TEMPLATE/test-template.md: Removed the markdown-based test case template.

• .github/ISSUE_TEMPLATE/test-template.yml: Created a new YAML-based test case template with structured fields for description, preconditions, steps, expected results, and additional notes.

Type Of Change

• 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 not to work as expected)
• Documentation update

Checklist

Code Only

• My code follows the project’s style guidelines.
• I have performed a self-review of my own code.
• I have commented on my code, particularly in hard-to-understand areas.
• I have added unit tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have ensured that my code does not introduce any errors or warnings.

Documents Only

• My documentation follows the project’s style guidelines.
• I have self-reviewed my document(s).
• I have checked my documentation for grammatical errors.
• I have ensured that my documentation is clear and easy to understand.

[MaximeTAlgosup]

LGTM 👍

[habicll]

looks good to me