[8.5](backport #3139) chore: fix linting

[mergify]

This is an automatic backport of pull request #3139 done by Mergify.

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[elasticmachine]

💔 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: 2022-10-20T08:45:00.367+0000

• Duration: 64 min 0 sec

Test stats 🧪

Test	Results
Failed	1
Passed	215
Skipped	0
Total	216

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_10_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-pod": context deadline exceeded 

• no stacktrace

Steps errors

Expand to view the steps failures

Start Elastic Stack

• Took 10 min 36 sec . View more details here
• Description: make -C .ci start-elastic-stack

Run tests in the node

• Took 15 min 19 sec . View more details here
• Description: make -C .ci run-tests

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_10_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.