[8.19](backport #5273) build(deps): bump github.com/elastic/elastic-agent-system-metrics from 0.11.18 to 0.12.0

[mergify]

Bumps github.com/elastic/elastic-agent-system-metrics from 0.11.18 to 0.12.0.

Release notes

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

v0.12.0

What's Changed

• feat: drop global ephemeralID by @​kruskall in elastic/elastic-agent-system-metrics#253
• refactor: replace lopg.ObserverLogs with logptest by @​kruskall in elastic/elastic-agent-system-metrics#252
• feat: replace global logging func with local logger by @​kruskall in elastic/elastic-agent-system-metrics#254
• feat: remove metric/memory package by @​kruskall in elastic/elastic-agent-system-metrics#251
• feat: replace global logger with local logger by @​kruskall in elastic/elastic-agent-system-metrics#255
• Revert "feat: remove metric/memory package" by @​kruskall in elastic/elastic-agent-system-metrics#256
• feat: deprecate NewReader and migrate to NewReaderOptions by @​kruskall in elastic/elastic-agent-system-metrics#257

Full Changelog: elastic/elastic-agent-system-metrics@v0.11.18...v0.12.0

Commits

• b387940 feat: deprecate NewReader and migrate to NewReaderOptions (#257)
• 53703d3 Revert "feat: remove metric/memory package" (#256)
• 2eadb5f feat: replace global logger with local logger (#255)
• eee5698 feat: remove metric/memory package (#251)
• 0ba9901 feat: replace global logging func with local logger (#254)
• 8382ef0 refactor: replace lopg.ObserverLogs with logptest (#252)
• 8cc791d feat: drop global ephemeralID (#253)
• 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 #5273 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 898abd5 has failed:

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

You are currently cherry-picking commit 898abd5.
  (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-fips.txt
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	both modified:   internal/pkg/api/metrics.go

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

[prodsecmachine]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[pchila]

There's a missing backport that is causing conflicts: context here

[pchila]

Missing backport of 13bea07 for using package github.com/elastic/fleet-server/v7/internal/pkg/logger/zap

Output of go mod tidy (after solving conflicts manually):

go: finding module for package github.com/elastic/fleet-server/v7/internal/pkg/logger/zap
go: github.com/elastic/fleet-server/v7/internal/pkg/api imports
        github.com/elastic/fleet-server/v7/internal/pkg/logger/zap: no matching versions for query "latest"

[elastic-sonarqube]

Quality Gate passed

Issues
1 New issue
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[pchila]

@ycombinator I guess that fleet-server FIPS server need a fix similar to elastic/elastic-agent#10007 until the staging environment is fixed