[beats receivers] Extension status is always present in status output in otel mode

[cmacknz]

• Relates [beats receivers] Surface which output configuration caused the collector to exit #9771

❯ sudo elastic-development-agent status
┌─ fleet
│  └─ status: (HEALTHY) Connected
└─ elastic-agent
   ├─ status: (HEALTHY) Running
   └─ extensions
      ├─ status: StatusOK
      ├─ extension:beatsauth/_agent-component/monitoring
      │  └─ status: StatusOK
      ├─ extension:elastic_diagnostics
      │  └─ status: StatusOK
      └─ extension:healthcheckv2/f3e9d497-3413-4e28-bef0-04f89a7bcdf2
         └─ status: StatusOK

Splitting this problem out of #9771 in case it's implementation is delayed. We need to hide the extension status from the default status output.

[elasticmachine]

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

[cmacknz]

We have all the extensions present now, we need a generic solution to hide them so I'm generalizing the title of this issue.

❯ sudo elastic-development-agent status
┌─ fleet
│  └─ status: (HEALTHY) Connected
└─ elastic-agent
   ├─ status: (HEALTHY) Running
   └─ extensions
      ├─ status: StatusOK
      ├─ extension:beatsauth/_agent-component/monitoring
      │  └─ status: StatusOK
      ├─ extension:elastic_diagnostics
      │  └─ status: StatusOK
      └─ extension:healthcheckv2/f3e9d497-3413-4e28-bef0-04f89a7bcdf2
         └─ status: StatusOK

[swiatekm]

My view of what we want to happen here:

• beatsauthextension status should be combined with the status of the respective output
  • How to combine this is not fully obvious, but something like the lower status wins, and concatenate messages together, should cover most cases.
• elastic_diagnostics should be blanket removed based on type - this extension is our implementation detail right now
• healthcheckv2 should be removed, but only the one we added, as the user might add their own

[cmacknz]

Agree, for the beatsauth extension Panos is working out how to do the association. In #9771 (comment) it may already be that the beatsauth extension causes the ES exporter status to change and we could potentially also just remove it.

[pkoutsovasilis]

#10412 ready for review