feat: update README for GitProxy v1.1.0 testing

[jescalada]

Retesting the fix for release-drafter.yml since labeling didn't work last time

[github-actions]

🔒 Automated Security Review

Security Review - No Issues Found

This PR only adds a comment line to the README.md file. No security concerns identified in this documentation-only change.

[github-actions]

Thanks for your contribution! I notice the PR description is quite brief and doesn't clearly explain what changes are being made or why.

Could you please provide a more detailed description that includes:

• What specific changes you're making to the README
• Why these changes are needed for GitProxy v1.1.0 testing
• What the previous issue was with release-drafter.yml and how this addresses it

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

This will help reviewers understand the context and purpose of your changes. Thanks!

[github-actions]

Thanks for the contribution! I notice a few things that need attention:

Description clarity: The current description is quite brief and doesn't clearly explain what changes are being made to the README or how they relate to GitProxy v1.1.0 testing. Could you provide more details about:

• What specific updates are being made to the README?
• How these changes relate to the release-drafter.yml fix?
• What the expected outcome should be?

Missing issue link: Please link this PR to an existing issue using keywords like "Fixes finos#123" or "Closes finos#123", or if no issue exists, consider creating one first to discuss the changes.

Contributing guidelines: According to the contributing guide, PRs should "Check for existing issues" and "link the relevant issue" in the PR description. This helps maintain traceability and ensures changes align with project goals.

A more descriptive PR description will help reviewers understand the context and purpose of these changes. Thanks!