[Feature]: Introduce structured GitHub issue templates

[BittuBarnwal7479]

Problem Statement

Issues can be opened in any format, often missing key details and slowing triage.

Proposed Solution

Add GitHub issue templates for:

Bug Reports

• Description
• Steps to reproduce
• Expected vs actual behavior
• Environment details
• Logs/screenshots
• Additional context

Feature Requests

• Problem statement
• Proposed solution
• Use case
• Alternatives considered
• Additional context

Alternatives Considered

Use a single generic issue template. However, separate templates provide more relevant guidance and improve issue quality.

Additional Context

Structured templates improve consistency, reduce clarification requests, and make triage more efficient.

Implementation Ideas

Add:

• .github/ISSUE_TEMPLATE/bug_report.md
• .github/ISSUE_TEMPLATE/feature_request.md

Optionally, add .github/ISSUE_TEMPLATE/config.yml to guide contributors to the appropriate template and related resources.

[hiSandog]

A useful next step might be to separate the repro into input, state/cache update, and final output for .github/ISSUE_TEMPLATE/bug_report.md. That would make it clearer whether “Introduce structured GitHub issue templates” is failing during parsing/configuration, during internal state updates, or only at the user-visible result.