chore: add metadata fields to issue templates for triage

[LagginTimes]

Description

This PR updates the GitHub issue templates bug_report.md and enhancement_request.md to improve triage and prioritization. Specifically, it adds structured fields for:

• Production impact (e.g., blocking usage vs. nice-to-have)
• Backend in use (Electrum, Esplora, RPC, etc.)
• Project or organization (optional, helps identify high-priority users)

The goal is to make it easier for maintainers to gauge the urgency and relevance of issues, especially for production users or high-impact integrations.

Checklists

All Submissions:

• I followed the contribution guidelines

[coveralls]

Pull Request Test Coverage Report for Build 16877003717

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 84.912%

---

Totals
Change from base Build 16786013135:	0.0%
Covered Lines:	6669
Relevant Lines:	7854

---

💛 - Coveralls

[nymius]

If this is for maintainers, perhaps enhancing the labeling system and status dashboards would be a better fit.

[LagginTimes]

If this is for maintainers, perhaps enhancing the labeling system and status dashboards would be a better fit.

I agree that better labels and status dashboards would help maintainers. In the meantime, this PR mirrors the template changes ACK’d for bdk and was requested for bdk_wallet (bitcoindevkit/bdk#1992). I’m +1 on discussing the labeling system and a maintainer dashboard as a follow-up, but I believe this PR helps keep both repos aligned and gives us immediate context to better prioritize issues.