[kibana] pass unique service.address value

[klacabane]

Summary

This change ensures all kibana metricsets set a unique service.address value. This is necessary for TSDB migration as we want to use this field as a dimension

How to test this PR locally

• ingest kibana data

metricbeat.modules:
  - module: kibana
    xpack.enabled: true
    period: 10s
    hosts: ["http://localhost:5601"]
    username: "elastic"
    password: "changeme"

• verify kibana metricsets publish the same unique value for service.address

Related issues

• Closes [kibana] only allow single value in service.address #37167

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @klacabane? 🙏.
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-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 52 min 16 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 51 min 34 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[miltonhultgren]

Looks good, seems similar to #36582