Backport of Add node id/name to config into release/1.16.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #17750 to be assessed for backporting due to the inclusion of the label backport/1.16.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@chapmanc
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: unable to process merge commit: "896e04ed616b432abfc501526fde55f6eef983a2", automatic backport requires rebase workflow

The below text is copied from the body of the original PR.

---

Description

We currently don't have node name in the NewDeps call. To add it we can keep tacking on new configuration values or we can add new values to the already existing config struct that is built in the builder.

There was a mini refactor required because the cfg is also used as an interface to instantiate the metricsClient. To reduce blast radius of a very large refactor I moved the instantiation of the metricsClient out of the sink initialization and then passed in the metricClient to the sink instead of passing the cfg in as an interface which stops us from using any of the values stored in the config.

I still think we should refactor the function for NewMetricsClient to not take an interface but for now I think this is an acceptable crawl step. We should work making this code a lot simpler as we are doing quite a bit with the "config" and treating it very much not as just config.

Testing & Reproduction steps

E2E tested with real consul-telemetry gateway and E2E test with mock HCP server is showing the labels flow through:

consul-k8s/acceptance ➜  kl fake-server-79c496b6c5-x42kb 
...
2023/06/15 23:08:53 Request Headers: map[Accept-Encoding:[gzip] Authorization:[Bearer mytoken] Content-Length:[29272] Content-Type:[application/x-protobuf] User-Agent:[Go-http-client/1.1] X-Channel:[consul/1.17.0-dev] X-Hcp-Resource-Id:[organization/11eb1a35-aac0-f7c7-8fe1-0242ac110008/project/11eb1a35-ab64-d576-8fe1-0242ac110008/hashicorp.consul.global-network-manager.cluster/TEST]]
2023/06/15 23:08:53 Request Labels: map[node_id:666b2fc3-6d6f-f86d-07af-3ea2b1560cba node_name:test-enmgay-consul-server-0]

consul-k8s/acceptance ➜  kg pods
NAME                                                       READY   STATUS             RESTARTS      AGE
fake-server-79c496b6c5-x42kb                               1/1     Running            0             2m17s
test-enmgay-consul-connect-injector-644b66d6f-bqgd8        1/1     Running            0             115s
test-enmgay-consul-server-0                                1/1     Running            0             115s
test-enmgay-consul-telemetry-collector-645f69ff9f-pzwc4    2/2     Running            0             115s
test-enmgay-consul-webhook-cert-manager-5c5d676978-pnv77   1/1     Running            0             115s

Links

n/a

PR Checklist

• updated test coverage
• [n/a] external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• 45b1ceb - 0701d01 - 507286f - 1d0b2dd - f2eb143 - 6fd48dd - c70fe10 - 3f8550e - 80ff6d3 - 896e04e - d50a6ae

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR

[chapmanc]

LGTM