[9.2] (backport #10785) [beatreceiver] add remaining inputs for our test use cases

[mergify]

What does this PR do?

Adds the Filebeat log, journald and winlog inputs. Also adds the Metricbeat kubernetes and linux metrics.

Why is it important?

Needed to test the otel runtime with the integrations and operating systems in our test cases.

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

Test system integration with _runtime_experimental set to otel for all inputs on Windows or Kubernetes integration with _runtime_experimental set to otel for all inputs.

Related issues

• Relates [beat_receiver] Add missing inputs for filebeatreceiver and metricbeatreceiver #9057

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?
• ...

---

This is an automatic backport of pull request #10785 done by [Mergify](https://mergify.com).

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)