ci: clean up release-drafter

[jescalada]

No description provided.

[github-actions]

Hi @jescalada! Thanks for contributing to GitProxy again.

I noticed this PR doesn't have a description. Could you please add one that explains:

• What changes you're making to the release-drafter configuration
• Why these changes are needed

Also, please link this PR to an existing issue using "Fixes #N", "Closes #N", or similar, or create a new issue if one doesn't exist yet.

Thanks!

[github-actions]

🔒 Automated Security Review

Security Review Summary

✅ No security issues found - This is a clean refactoring of the release-drafter workflow.

Analysis

The changes in this PR are focused on workflow cleanup and actually improve security in one key area:

• Improved action pinning: The workflow now pins release-drafter/release-drafter to a specific commit hash (563bf132657a13ded0b01fcb723c5a58cdd824e2) instead of using the potentially mutable @v6 tag, which is a security best practice.
• Appropriate permissions: The workflow maintains proper permission scoping with contents: write for creating releases.
• Secure token usage: Continues to use the standard GITHUB_TOKEN secret appropriately.

The removal of pull request triggers and permission adjustments appear to be legitimate workflow optimizations without security implications.