ci: fix gh status check

[v1v]

As pointed in the below comment:
#362 (comment)

[ghost]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-01-24T21:36:28.678+0000

• Duration: 8 min 2 sec

Test stats 🧪

Test	Results
Failed	1
Passed	207
Skipped	2
Total	210

Test errors

Expand to view the tests failures

Test / Matrix - PLATFORM = 'ubuntu-18 && immutable' / Test / Test_handleInfoRequest – github.com/elastic/apm-aws-lambda/apmproxy

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   Test_handleInfoRequest
    logger.go:130: 2023-01-24T21:44:19.726Z	INFO	Extension listening for apm data on 127.0.0.1:1234
    receiver_test.go:201: 
        	Error Trace:	receiver_test.go:201
        	Error:      	Received unexpected error:
        	            	Post "http://127.0.0.1:1234/intake/v2/events": EOF
        	Test:       	Test_handleInfoRequest
    logger.go:130: 2023-01-24T21:44:19.727Z	DEBUG	server closed
--- FAIL: Test_handleInfoRequest (0.00s)
 

Steps errors

Expand to view the steps failures

Running Go tests

• Took 1 min 32 sec . View more details here
• Description: gotestsum --format testname --junitfile junit-report.xml -- -v ./...

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)