Implement GitHub Issue Templates for bug reports and feature requests

[Nitya-003]

Description

Currently, when a user or contributor opens a new issue, they are presented with a blank text box. This often leads to incomplete information, requiring maintainers to manually ask for logs, component details, or steps to reproduce.

To streamline the development workflow for DSCWOC, I propose adding standardized GitHub Issue Templates.

Proposed Solution

I will implement a .github/ISSUE_TEMPLATE/ directory containing two core templates:
1. Bug Report Template: Fields for: Steps to reproduce, Expected vs. Actual behavior, Browser/OS details, and screenshots of the compatibility error.
2. Feature Request Template: Fields for: Problem statement, Proposed solution, and potential impact on the lib/ logic (Compatibility/Suggestions engine).

Tasks

• Create the .github/ISSUE_TEMPLATE/ directory.
• Create bug_report.md.
• Create feature_request.md.

Why this is needed

1. Better Data: Ensures developers get the specific PC parts or build configurations that caused a bug.
2. Maintainer Sanity: Reduces the time spent on "triaging" issues and asking for more information.
3. Project Maturity: Standardizes the repository for professional open-source participation.

I can set up these Markdown templates to match the Next.js 15 / shadcn tech stack of RigCrafter. Please assign this to me!

Labels: chore, documentation, community, DSCWOC

[github-actions]

Thank you for raising this issue!

We'll review it as soon as possible. We truly appreciate your contributions! ✨

Meanwhile make sure you've visited the README.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md before creating a PR for this. Also, please do NOT create a PR until this issue has been assigned to you. 😊

[SamXop123]

@Nitya-003 Assigned! You can now proceed to add the pr