Bump github.com/elastic/go-sysinfo to v1.15.0

[swiatekm]

This update includes a notable performance improvement for determining host ip addresses.

It looks like dependabot is currently blocked by a bunch of large collective updates, so I'm submitting this separately.

Related issues

• Relates Elastic agent uses too much memory per Pod in k8s elastic-agent#5835

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @swiatekm? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[andrewkroh]

You'll need a make notice.

[andrewkroh]

I think a changelog entry is warranted that identifies under what scenarios users might see reduced memory usage.

[swiatekm]

I think a changelog entry is warranted that identifies under what scenarios users might see reduced memory usage.

I don't really want to quantify the improvement, because it's highly dependent on the environment and configuration. A situation where this comes up in my testing is when beats are monitored over the http /stats endpoint and this calls the function registered here, eventually leading to a sysinfo.Host call. This is a temporary allocation, so whether it makes a difference for a given user is hard to predict.

Honestly, this is mostly for my own peace of mind. I spend a lot of time profiling agent and beats in Kubernetes nowadays, and this distracts me every time it shows up. 😅