feat(github): enrich comment event body for CEL evaluation

[theakshaypant]

📝 Description of the Change

When processing comment events on GitHub, we now enrich the event body with the complete pull request data. This allows CEL expressions to access all pull request details when evaluating conditions on comment webhooks (/test, /retest, /ok-to-test).

👨🏻‍ Linked Jira

https://issues.redhat.com/browse/SRVKP-8617

🔗 Linked GitHub Issue

N/A

🚀 Type of Change

• [ ] 🐛 Bug fix (fix:)
• [x] ✨ New feature (feat:)
• [ ] 💥 Breaking change (feat!:, fix!:)
• [ ] 📚 Documentation update (docs:)
• [ ] ⚙️ Chore (chore:)
• [ ] 💅 Refactor (refactor:)
• [ ] 🔧 Enhancement (enhance:)
• [ ] 📦 Dependency update (deps:)

🧪 Testing Strategy

• [x] Unit tests
• [ ] Integration tests
• [ ] End-to-end tests
• [x] Manual testing
• [ ] Not Applicable

🤖 AI Assistance

• [ ] I have not used any AI assistance for this PR.
• [x] I have used AI assistance for this PR.

If you have used AI assistance, please provide the following details:

Which LLM was used?

• [ ] GitHub Copilot
• [ ] ChatGPT (OpenAI)
• [ ] Claude (Anthropic)
• [x] Cursor
• [ ] Gemini (Google)
• [ ] Other: ____________

Extent of AI Assistance:

• [ ] Documentation and research only
• [ ] Unit tests or E2E tests only
• [ ] Code generation (parts of the code)
• [ ] Full code generation (most of the PR)
• [ ] PR description and comments
• [x] Commit message(s)

[!IMPORTANT] If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message. For example:

Co-authored-by: Gemini [email protected] Co-authored-by: ChatGPT [email protected] Co-authored-by: Claude [email protected] Co-authored-by: Cursor [email protected] Co-authored-by: Copilot [email protected]

**💡You can use the script ./hack/add-llm-coauthor.sh to automatically add these co-author trailers to your commits.

✅ Submitter Checklist

• [x] 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
• [x] ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
• [x] ♽ I have run make test and make lint locally to check for and fix any issues. For an efficient workflow, I have considered installing pre-commit and running pre-commit install to automate these checks.
• [x] 📖 I have added or updated documentation for any user-facing changes.
• [ ] 🧪 I have added sufficient unit tests for my code changes.
• [ ] 🎁 I have added end-to-end tests where feasible. See README for more details.
• [ ] 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
• [ ] If adding a provider feature, I have filled in the following and updated the provider documentation:
  • [ ] GitHub App
  • [ ] GitHub Webhook
  • [ ] Gitea/Forgejo
  • [ ] GitLab
  • [ ] Bitbucket Cloud
  • [ ] Bitbucket Data Center