Add filebeat receiver to OTEL components

[blakerouse]

What does this PR do?

Adds the fbreceiver (aka. filebeat receiver) to OTel receivers that the Elastic Agent OTel supports.

Why is it important?

Adds the ability to run filebeat inputs as an OTel receiver.

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 (will be tested in integration test)
• 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

None.

How to test this PR locally

Run elastic-agent otel with an OTel configuration (otel.yml) like the following:

receivers:
  filebeatreceiver:
    filebeat:
      inputs:
        - type: benchmark
          enabled: true
          message: "test"
		  eps: 5
    output:
      otelconsumer:
    logging:
      level: debug
      selectors:
        - '*'
    processors:
      - add_fields:
          target: project
          fields:
            name: myproject
processors:
  batch:
exporters:
  debug:
    verbosity: detailed
    sampling_initial: 100
service:
  pipelines:
    logs:
      receivers: [filebeatreceiver]
      processors: [batch]
      exporters: [debug]

[mergify]

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

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

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[blakerouse]

With all the needed changes in beats complete importing beats into the elastic-agent now works. This PR has the fbreceiver working. Still in Draft as I work on adding an integration test for coverage.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fbreceiver upstream/fbreceiver
git merge upstream/main
git push upstream fbreceiver

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[blakerouse]

Closing in favor of #5672