Fix feature request template link in CONTRIBUTING.md

[Copilot]

The "Add New Feature" link in CONTRIBUTING.md referenced a non-existent feature_request.md template, causing users to land on a blank issue form instead of the structured feature proposal template.

Changes

• Updated link from template=feature_request.md to template=feature_proposal.yml
• Removed redundant URL parameters (labels, title) already defined in the YAML template

The link now correctly routes to .github/ISSUE_TEMPLATE/feature_proposal.yml, which contains structured fields for Overview, Usage example, Breaking change status, and Alternatives.

PR Checklist

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• PR doesn't include merge commits (always rebase on top of our main, if needed)
• New integration
  • [N/A] Docs are written
  • [N/A] Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• [N/A] Tests for the changes have been added (for bug fixes / features) (if applicable)
• Contains NO breaking changes
• [N/A] Every new API (including internal ones) has full XML docs
• Code follows all style conventions

Other information

Documentation-only change. No code modifications.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Improved Feature Submission Documentation</issue_title>
<issue_description>### Page URL

https://github.com/CommunityToolkit/Aspire?tab=contributing-ov-file

Describe the issue

On clicking the link to in the "Add New Feature" it does not take you to the feature template but instead takes you to a blank feature. If this is the desired behavior that is fine but you do not provide any additional information that informs the user that there is a much more detailed new feature template and if they are not aware of this like myself then they will submit an entire feature request, with a great deal of detail as is asked, without realizing they should instead be selecting a specific template that is more suited to what the repo desires. The first image shows the documentation where I clicked the link to submit my earlier feature proposal, the second image is the template I was sent to and which I filled out a full proposal, and the third image is the most well suited, IMO, template for what that link suggests

Suggestion

Edit the link to point to the actual new feature template rather than the blank template

Additional context

I will delete my previous issue I added and refactor it to match your actual new feature template so that it is not deleted without being read though I clearly followed the directions in the contributors guideline by following the link that is posted

Help us help you

No, just wanted to report this</issue_description>

<agent_instructions>looks like the wrong template is referenced - update to use the right one</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Improved Feature Submission Documentation #1047

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

This PR fixes a broken link in the contributing documentation that was directing users to a non-existent issue template. The link now correctly points to the structured YAML-based feature proposal template.

Key Changes

• Updated the feature request template reference from feature_request.md to feature_proposal.yml
• Removed redundant URL parameters (labels and title) that are already defined within the YAML template