[SPARK-37879][INFRA] Show test report in GitHub Actions builds from PRs

[HyukjinKwon]

What changes were proposed in this pull request?

This PR proposes to show the link of Check run view instead of Actions view. Previously, when you add a new custom Check, e.g., test_report.yml, Actions view also showed this Check.

Now, seems GitHub Actions changed the behaviour - Actions view always includes the jobs initiated by the specific Workflow e.g., build_and_test.yml does not include the custom Check added from test_report.yml.

To work around this problem, this PR proposes to show the link of:
Check run view e.g., https://github.com/apache/spark/runs/4785069876 ("Report test results" is included) instead of
Actions view e.g., https://github.com/apache/spark/actions/runs/1686013487 ("Report test results" is missing) .

After this PR, when developers click the link here:

it will open a Check run view instead of Actions view which does not have test report tab.

Why are the changes needed?

For developers to see the test report, and they can easily detect which test is failed.

Does this PR introduce any user-facing change?

No, dev-only

How was this patch tested?

Manually tested at HyukjinKwon#51.

[HyukjinKwon]

cc @gengliangwang @Yikun @dongjoon-hyun @cloud-fan @ueshin FYI

[Yikun]

I have roughly know the purpose of this PR, looks good. One question, is it necessary to link to "Report test results" directly instead of "Configure Jobs"? That is https://github.com/apache/spark/runs/4785827549 in your example.

(BTW, I didn't even realize we had this test report before. 😂)

[dongjoon-hyun]

+1, LGTM. Thank you, @HyukjinKwon and all.
Merged to master.

[HyukjinKwon]

Thanks @dongjoon-hyun and @Yikun!

One question, is it necessary to link to "Report test results" directly instead of "Configure Jobs"? That is https://github.com/apache/spark/runs/4785827549 in your example.

Yeah, I thought about this but the problem is that when the jobs are in a queue (triggered but not started yet), it only has two states Configure jobs and Check changes. So, the job cannot be linked until Report test results appears but this is the end of tests that could take few hours ..

[Yikun]

@HyukjinKwon Looks like update_build_status job is worked unexpectly after this PR. Such as this PR: #35183, it is stucked in "queued" status.

I also took a look on update job, it raised 404 in update_build_status job, it was wrong to get the run_id on https://api.github.com/repos/Yikun/spark/actions/runs/4797718278, but the right api should be https://api.github.com/repos/Yikun/spark/actions/runs/1690601631.

There are 2 potential workaround make update_build_status work I guess:

Workaround 1, still return the old runID in here:

spark/.github/workflows/notify_test_workflow.yml

Line 125 in 21ad3da

run_id: runID

Workaround 2, Get right action id according new runID

spark/.github/workflows/update_build_status.yml

Line 68 in 21ad3da

run = await github.request('GET /repos/{owner}/{repo}/actions/runs/{run_id}', params)

[HyukjinKwon]

oh yeah. I think we can fix it with workaround 2.

[HyukjinKwon]

Fixed in #35189. Let's see how it goes. Thanks @Yikun!

[Yikun]

New PR: #35193