[beats receivers] The diagnostics state.yaml should indicate which runtime is used for each component

[cmacknz]

When enabling beats receivers for monitoring and looking at diagnostics, there is no way to tell from the state.yaml which components and inputs are being run in the OpenTelemetry collector.

We should include the runtime for each component explicitly to make this easier to see.

This in pre-config.yaml

agent:
    download:
        sourceURI: https://artifacts.elastic.co/downloads/
    features: null
    monitoring:
        _runtime_experimental: otel
        enabled: true
        logs: true
        metrics: true

results in the following in state.yaml for the filestream-monitoring component

    - id: filestream-monitoring
      state:
        component_idx: 0
        features_idx: 0
        message: HEALTHY
        pid: 0
        state: 2
        units:
            input-filestream-monitoring-filestream-monitoring-agent:
                message: Healthy
                payload:
                    streams:
                        filestream-monitoring-agent:
                            error: ""
                            status: HEALTHY
                state: 2
            output-filestream-monitoring:
                message: Healthy
                state: 2

[elasticmachine]

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

[swiatekm]

This is already included;

    - id: filestream-default
      state:
        component_idx: 0
        features_idx: 0
        message: HEALTHY
        pid: 0
        state: 2
        units:
            input-filestream-default-filestream-system:
                message: Healthy
                state: 2
            output-filestream-default:
                message: Healthy
                state: 2
        version_info:
            build_hash: f4d9097cac81508b3f53c6fbbe97c7077484a185
            meta:
                build_time: 2025-09-22 11:02:12 +0000 UTC
                commit: f4d9097cac81508b3f53c6fbbe97c7077484a185
            name: beats-receiver  # <-- this is different for beats processes

It's part of the status output and we use it in integration tests.

[cmacknz]

Closing, this is good enough as is.