Add component.{id, binary} to monitoring metrics

[belimawr]

What does this PR do?

This PR adds component.id and component.binary to the monitoring metrics, those fields are necessary to create unique TSDB entries.

Why is it important?

It fixes metrics collection.

Checklist

• My code follows the style guidelines of this project
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have made corresponding changes to the documentation
  - [ ] I have made corresponding change to the default configuration files
  - [ ] I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
  - [ ] I have added an integration test or an E2E test

Author's Checklist

• This PR works with Logstash output

How to test this PR locally

See the "How to test this PR locally" section from the integrations PR: elastic/integrations#8238

Related issues

• Relates Improve and unify dimensions for Elastic-Agent and Beats metrics integrations#8238
• Closes [Elastic Agent] TSDB metrics dimensions do not create unique time series integrations#7977

## Use cases
## Screenshots
## Logs

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @belimawr? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

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

NOTE: backport-skip has been added to this pull request.

[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

• Start Time: 2023-11-03T15:06:26.259+0000

• Duration: 72 min 23 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.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

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

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	98.824% (84/85)	👍
Files	66.885% (204/305)	👍
Classes	66.071% (370/560)	👍
Methods	53.339% (1174/2201)	👍
Lines	39.639% (13818/34860)	👍 0.107
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[pchila]

LGTM

[cmacknz]

We should backport to v8.11 as this is part of the bug fix for duplicated TSDB documents in the elastic agent integration.

[blakerouse]

Changes looks good!

[elastic-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

76.6% Coverage
16.0% Duplication