[8.17](backport #4436) build(deps): bump github.com/elastic/elastic-agent-libs from 0.18.5 to 0.18.6

[mergify]

Bumps github.com/elastic/elastic-agent-libs from 0.18.5 to 0.18.6.

Release notes

Sourced from github.com/elastic/elastic-agent-libs's releases.

v0.18.6

What's Changed

• build(deps): bump golang.org/x/crypto from 0.24.0 to 0.32.0 by @​dependabot in elastic/elastic-agent-libs#275

Full Changelog: elastic/elastic-agent-libs@v0.18.5...v0.18.6

Commits

• 8a76ed0 build(deps): bump golang.org/x/crypto from 0.24.0 to 0.32.0 (#275)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

This is an automatic backport of pull request #4436 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of ff1e859 has failed:

On branch mergify/bp/8.17/pr-4436
Your branch is up to date with 'origin/8.17'.

You are currently cherry-picking commit ff1e859.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	both modified:   testing/go.mod
	both modified:   testing/go.sum

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[swiatekm]

buildkite test this

[michel-laterman]

@dependabot rebase

[mergify]

This pull request is now in conflicts. Could you fix it @mergify[bot]? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.17/pr-4436 upstream/mergify/bp/8.17/pr-4436
git merge upstream/8.17
git push upstream mergify/bp/8.17/pr-4436

[swiatekm]

Looks like the test failures are due to the min TLS version going up to 1.2. I thought #4238 was supposed to address that, but the failures show up in ES config tests. @michel-laterman can you have a look?

[mergify]

This pull request has not been merged yet. Could you please review and merge it @swiatekm? 🙏

[michel-laterman]

The changes from #4238 were not backported to 8.17; I've added them to this PR

[jlind23]

buildkite test it

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube