set path.home for beat receivers to be components dir

[leehinman]

What does this PR do?

sets path.home for beat receivers to be the components dir.

Why is it important?

This is necessary so metricbeat receiver gets the correct directory to
find light modules

Checklist

• I have read and understood the pull request guidelines of this project.
• 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

Disruptive User Impact

How to test this PR locally

Unit test

cd internal/pkg/otel/translate
go test .

By hand

1. build agent
2. enroll with policy that has activemq metrics
3. override so all metrics are collected with metricbeat receiver

PUT kbn:/api/fleet/agent_policies/<policy_id>
{
    "name": "test",
    "namespace": "default",
    "overrides": {
        "agent": {
            "internal": {
                "runtime": {
                    "metricbeat": {
                        "default": "otel"
                    }
                }
            }
        }
    }
}
4. verify activemq metrics starts

Related issues

• Closes [metricbeatreceiver] activemq metricsets not found beats#48010

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 @leehinman? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: ca1b5b9

Failed CI Steps

• x86_64:sudo: fleet - platform-ingest-elastic-agent-debian-13-1762801856

cc @leehinman