ci: rerun failing checks on dependency upgrade PRs CLOUDP-396684

[ivandevp]

Description

Rerun evergreen checks for dep upgrade PR so that we can see on next run if checks are passing or let a maintainer just manually approve and merge without needing to rerun all checks again.

A test was done by manually triggering the action in https://github.com/mongodb-js/compass/actions/runs/24468672109/job/71502724447

Logs found during this test:

Found failed Evergreen checks:
https://evergreen.mongodb.com/build/10gen_compass_main_unit_tests_windows_patch_54bbb36a13a44bdc446fbe98d8eac390bd646a4a_69df9bb49173ce0007fe5a99_26_04_15_14_07_51
https://evergreen.mongodb.com/build/10gen_compass_main_package_windows_patch_54bbb36a13a44bdc446fbe98d8eac390bd646a4a_69df9bb49173ce0007fe5a99_26_04_15_14_07_51
https://evergreen.mongodb.com/build/10gen_compass_main_generate_vulnerability_report_patch_54bbb36a13a44bdc446fbe98d8eac390bd646a4a_69df9bb49173ce0007fe5a99_26_04_15_14_07_51
https://evergreen.mongodb.com/build/10gen_compass_main_test_web_sandbox_patch_54bbb36a13a44bdc446fbe98d8eac390bd646a4a_69df9bb49173ce0007fe5a99_26_04_15_14_07_51
Restarting failed tasks for Evergreen version: 69df9bb49173ce0007fe5a99
Successfully scheduled restart for version 69df9bb49173ce0007fe5a99

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• If this change updates the UI, screenshots/videos are added and a design review is requested
• If this change could impact the load on the MongoDB cluster, please describe the expected and worst case impact
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)