mod: update elastic/mito to version v1.9.0

[efd6]

Proposed commit message

See title.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a8a9f9b

cc @efd6

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a8a9f9b

cc @efd6

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a8a9f9b

cc @efd6

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a8a9f9b

cc @efd6

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a8a9f9b

cc @efd6

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a8a9f9b

cc @efd6

[elasticmachine]

💚 Build Succeeded

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

Expand to view the summary

Build stats

• Duration: 192 min 56 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

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

[efd6]

Ooop