fix(github-bot): handle pull_request_review event from fork

[aeddi]

This PR fixes this issue: #3238 (comment)

In summary, the pull_request_review event, when emitted from a PR opened from a fork, only allows the GitHub Bot workflow to run with read-only permissions.

This PR addresses this issue by:

• Ensuring that the GitHub Bot workflow does not fail in the case of a read-only run, but simply saves the number of the PR to be processed by uploading a file containing the number as an artifact (which is possible even in read-only mode).
• Adding a new GitHub Bot Proxy workflow that monitors all completed runs of the GitHub Bot through a subscription to the workflow_run event.
• If a run of the GitHub Bot workflow concerns a pull_request_review event, the GitHub Bot Proxy workflow retrieves the artifact containing the PR number and then re-runs the GitHub Bot workflow using a workflow_dispatch event.
• The GitHub Bot workflow then runs again, but this time with write permissions, allowing it to update its comment or the status of its CI check, among other things.

[Gno2D2]

🛠 PR Checks Summary

🔴 The pull request head branch must be up-to-date with its base (more info)

Manual Checks (for Reviewers):

• SKIP: Do not block the CI for this PR

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🔴 The pull request head branch must be up-to-date with its base (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: aeddi/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

The pull request head branch must be up-to-date with its base (more info)

If

🟢 Condition met
└── 🟢 On every pull request

Then

🔴 Requirement not satisfied
└── 🔴 Head branch (aeddi:dev/aeddi/bot-fix-review) is up to date with base (master): behind by 2 / ahead by 2

Manual Checks

**SKIP**: Do not block the CI for this PR

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[thehowl]

hacky, but LGTM.

summoning the action masters @ajnavarro @sw360cab for a second review