Update module go.elastic.co/apm/module/apmelasticsearch/v2 to v2.2.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
go.elastic.co/apm/module/apmelasticsearch/v2	require	minor	v2.1.0 -> v2.2.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[naemono]

note for context elastic/apm-agent-go#1274

and

21:38:34 [pkg/controller/common/tracing/apmclientgo/client.go:73 SA1019: span.Context.SetDestinationService is deprecated: use SetServiceTarget (staticcheck)
21:38:34 span.Context.SetDestinationService(apm.DestinationServiceSpanContext{

[naemono]

@elasticmachine run elasticsearch-ci/docs

[pebrc]

This change has some undesirable consequences for our current monitoring cluster which runs 8.4.x not sure if the corresponding UI changes will in 8.5?

Compare (top: old, bottom: new):

and (top: old, bottom: new)

IP instead of service name, the relevant information "Kubernetes API server" is somehow lost in the UI. I can try with 8.4 tomorrow or we upgrade our monitoring to 8.5 which might be a good idea anyway.

[pebrc]

I think I would keep the deprecated fields in use with a linter exception as long as the UI does not handle the new fields (does not seem to be the case in 8.5 yet)

[naemono]

@pebrc I've adjusted this to ignore the deprecation in this file, and reverted the code changes for now.

[thbkrkr]

@elasticmachine run elasticsearch-ci/docs

[naemono]

@elasticmachine run elasticsearch-ci/docs

(why did it not run yesterday, I wonder)