Is your feature request related to a problem? Please describe.

The [RepoBot.js] script is a crucial piece of automation for the repository, responsible for notifying contributors when their PRs are published in a release. While it functions correctly, its current structure could be improved for better robustness, easier debugging, and long-term maintainability.

Specifically, the notifyPRPublished function has some areas for enhancement:

1. Redundant Code: The initial try...catch block for fetching a PR is very similar to the logic already present in the _getPR helper function, leading to code duplication.

2. Limited Error Granularity: The error handling is somewhat generic. Distinguishing between different types of errors (e.g., a PR not being found vs. a GitHub API server error) would make the script more resilient.

3. Monolithic Function: The notifyPRPublished function handles multiple responsibilities: fetching data, checking several conditions, and posting comments. This makes it complex to read and modify.

Describe the solution you'd like

I propose refactoring [RepoBot.js] to address these points. The goal is to make the script more modular, resilient, and easier to understand for future contributors.

Here are the specific changes I suggest:

Consolidate PR Fetching Logic: Utilize the existing _getPR(id) helper method within notifyPRPublished to remove the redundant try...catch block and centralize the logic for fetching a pull request.

Refactor notifyPRPublished: Break down the function into smaller, more focused helper methods. This follows the single-responsibility principle and improves readability. For example:

A new _isEligibleForNotification(pr) method to encapsulate the checks for whether a PR is merged, authored by a bot, or from a collaborator.
The existing _hasBeenNotified(comments) method is already a great example of this pattern.
Enhance Logging for Clarity: Add more descriptive log messages to provide better insight into the script's execution flow, especially for skipped PRs. For example, logging the specific reason a PR was skipped

Describe alternatives you've considered

No response

Additional context/Screenshots