Skip buildkite steps for branches for dependabot PRs

[geriux]

This PR aims to block Buildkite steps to run on the Dependabot PRs we have for the submodules, Jetpack, Block experiments, and Gutenberg.

We are constantly seeing failed CI checks due to a pre-existing build on S3. Until there's a solution for that, I propose blocking the steps so we don't have failures on those PRs.

There will be a button to manually run these steps on these branches:

There's no need to have Android builds uploaded for these PRs since as far as I know we never make main apps PRs targeting those PRs.

To test

CI checks should pass and Builtkite steps should be blocked.

This other PR #5477 that has the same changes but with a different branch name should run all Builtkite steps without manually approving the steps.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

[fluiddot]

LGTM 🎊 !

As you mentioned in the PR's description is very unlikely that we merge a Dependabot PR, as we mainly use it for spotting breakages from the submodules. My only concern is, based on the PR's job status, how clear is that those jobs are blocked and required to be manually triggered. I don't see it as a critical issue as once you go to the Buildkite job you see the button but I understand that for someone without this context, it might be a bit confusing the first time.

[geriux]

My only concern is, based on the PR's job status, how clear is that those jobs are blocked and required to be manually triggered. I don't see it as a critical issue as once you go to the Buildkite job you see the button but I understand that for someone without this context, it might be a bit confusing the first time.

Yeah that's a valid concern, I thought about making those check statuses optional but I'd be worried about people merging with those checks failing or enabling auto merging and accidentally breaking something. Let's merge and see if it becomes an issue in the day-to-day workflows.

For this PR for example, I need to run the tests so I can merge 😄 so let's see.

Thank you for the review!