[ci] make GitHub Actions branch protection stricter (fixes #5501)

[jameslamb]

Fixes #5501.

Following advice in that issue and in https://github.com/orgs/community/discussions/26733#discussioncomment-3253155, this proposes two changes to the project's GitHub Actions jobs.

• use https://github.com/re-actors/alls-green to enforce multiple checks passing without needing to change branch protection settings every time checks are added or removed
• give each of those "all the checks passed" jobs a unique name

This will make use of GitHub auto-merging more reliable, and reduce the risk of accidentally merging PRs where some CI jobs are failing.

Notes for Reviewers

@guolinke @shiyu1994 can you please go into the branch protection for master at https://github.com/microsoft/LightGBM/settings/branches and modify the section Require status checks to pass before merging?

The following should be checked as required:

• all-cuda-jobs-successful (GitHub Actions)
• all-optional-checks-successful (GitHub Actions)
• all-python-package-jobs-successful (GitHub Actions)
• all-r-package-jobs-successful (GitHub Actions)
• all-static-analysis-jobs-successful (GitHub Actions)

And the following should be unchecked:

• all-successful (GitHub Actions)

I think that only the two of you have permissions in this repo to modify that.

[guolinke]

I think i don't have permission to do it, ping @shiyu1994

[shiyu1994]

@jameslamb Done with that.

[jameslamb]

thanks @shiyu1994 ! As soon as this is approved, let's merge it.

[shiyu1994]

LGTM

[jameslamb]

Thanks so much @shiyu1994 !

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed.
To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues
including a reference to this.