docs(374): 📝 add feature request template

[SeanAlexanderHarris]

helps users submit requests for new features or enhancements in a structured way

[prolific-snyk]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[Copilot]

Pull request overview

Adds a GitHub Issue Form template to help users submit feature requests in a structured, repeatable format for this CLI project.

Changes:

• Introduces a new Feature Request issue form with an intro message.
• Adds two required textarea prompts (problem + proposed solution).
• Applies the enhancement label to submitted feature requests.

[Copilot]

To keep issue templates consistent with the existing bug report form, consider adding the same top-level metadata fields here (e.g., a title prefix and the type field). BUG_REPORT.yml includes title and type, which helps with consistent issue naming and categorization in GitHub.

Suggested change

	description: Suggest an idea, feature, or enhancement
	description: Suggest an idea, feature, or enhancement
	title: "[Feature Request]: "
	type: Feature

[Copilot]

The textarea fields don’t have id values. In BUG_REPORT.yml, each form element has an id, which makes the submitted form data stable for future automation (and avoids ambiguity if labels change). Consider adding unique ids for these textareas (and optionally descriptions/placeholders like the bug template does).

Suggested change

	- type: textarea
	attributes:
	label: What is the problem this would solve and/or feature it would enhance?
	validations:
	required: true
	- type: textarea
	- type: textarea
	id: problem
	attributes:
	label: What is the problem this would solve and/or feature it would enhance?
	validations:
	required: true
	- type: textarea
	id: proposal

[benmatselby]

LGTM