chore: add release contributors section

[AkashKumar7902]

Summary

• Add a Contributors section to the Release Drafter template using $CONTRIBUTORS.
• Keep the existing release categories, labels, and version resolver unchanged.

Fixes #831

Validation

• yq '.' .github/release-drafter.yml
• yq -e '.template == "$CHANGES\n\n## Contributors\n\n$CONTRIBUTORS\n"' .github/release-drafter.yml
• git diff --check

[Copilot]

Pull request overview

Adds a Contributors section to this repository’s Release Drafter-generated release notes to satisfy issue #831’s requirement that GitHub Releases include the list of people who contributed to the release.

Changes:

• Update Release Drafter template to append a “## Contributors” section.
• Populate that section using Release Drafter’s $CONTRIBUTORS placeholder.

---

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

[jvanz]

@AkashKumar7902 you need to fix the commit signature to allow us to merge this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.43%. Comparing base (88b4b9c) to head (36cfb0f).
⚠️ Report is 71 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1690      +/-   ##
==========================================
+ Coverage   75.53%   80.43%   +4.90%     
==========================================
  Files         170      127      -43     
  Lines       20900    16413    -4487     
==========================================
- Hits        15786    13202    -2584     
+ Misses       4902     3211    -1691     
+ Partials      212        0     -212     

Flag	Coverage Δ
go-tests	?
rust-tests	80.43% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[AkashKumar7902]

I checked this one. The current head commit is unsigned, and the local SSH key available in this environment is not registered as a GitHub signing key. I also tried to add it as a signing key, but the current gh token does not have admin:ssh_signing_key, so GitHub rejects that API call.

I am not force-pushing a locally signed unknown_key commit because that would still fail the verified-signature requirement. This needs either re-signing with a key already registered in GitHub as a signing key, or registering the available key first and then re-signing.