Fix feature request issue template label

[logical34]

Description

This small bounty/improvement PR fixes the feature request issue template to use an existing repository label.

The template currently declares labels: [Feature], but this repository does not have a Feature label. GitHub issue forms do not create missing labels automatically, so feature request issues opened through this template will not receive the intended triage label.

This PR changes the template to use the existing enhancement label, matching the repository's current label set.

Verification

• Parsed .github/ISSUE_TEMPLATE/feature_request.yml with PyYAML.
• Confirmed the template now resolves to ['enhancement'].
• Confirmed enhancement exists in the repository labels via gh label list --repo BitgesellOfficial/bitgesell.
• Ran git diff --check.

Bounty / payout

Submitted for the Bitgesell PR bounty/improvement program: refs #32 and #39.

If approved, USDT/EVM-compatible payout address:

0xd6634800410978b62D4a2317dCAF2871CDa9e1D3

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the Feature Request GitHub issue form to apply the standard enhancement label instead of Feature.

Changes:

• Switch default label in the feature request issue template from Feature to enhancement.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[MyTH-zyxeon]

Maintainer-facing review assist for the #32/#39 bounty routing:

I rechecked this PR as a small issue-template triage fix. It is OPEN / MERGEABLE with mergeStateStatus=CLEAN at head d40acf512cb4bf9235665e44a58586f64941ee75, and I only see the Copilot review note so far.

Scope is narrow: one line in .github/ISSUE_TEMPLATE/feature_request.yml, changing labels: [Feature] to labels: [enhancement]. I also checked the current repository label set: enhancement exists and Feature does not, so the issue-form label rationale is valid.

Pre-merge checks I would ask for:

• Confirm maintainers want feature requests routed to enhancement rather than recreating/renaming a historical Feature label.
• Treat this as small template/triage hygiene for BGL PR bounty hunt #32/BGL PR bounty hunt ($10000 overall budget) #39 payout classification; issue BGL PR bounty hunt ($10000 overall budget) #39 says one-line/comment-editing style changes may receive a lesser payout.
• If the intended workflow is just the existing enhancement label, this looks merge-ready; no code change requested from the author.

No live-chain, wallet, or payment action is involved here.