Status command is inconsistent between `full`, `json` and `yam`

[AndersonQ]

• Version: 8.12.0 and older, main
• Operating System: all
• Discuss Forum URL: N/A
• Steps to Reproduce: run the status command with --outout full|json|yaml, they will differ in the information they show:

The full version of the status command output does not include the components version or build hash (do not mistake version_info.build_hash with version_info.meta.commit).

Components using the version 7.8.0+ of the control protocol the status command should report their version_info.build_hash, for components using older versions of the protocol, the version_info.version.

output difference

• elastic-agent status --output full

  ┌─ fleet
  │  └─ status: (HEALTHY) Connected
  └─ elastic-agent
  ├─ status: (HEALTHY) Running
  ├─ info
  │  ├─ id: 7c2067ff-30ff-4628-b8cf-af36fa56a524
  │  ├─ version: 8.12.0
  │  └─ commit: 5cbf2e403c761f91d11eca6b9cb5385e0f07f2ce
  ├─ beat/metrics-monitoring
  │  ├─ status: (HEALTHY) Healthy: communicating with pid '2343'
  │  ├─ beat/metrics-monitoring
  │  │  ├─ status: (HEALTHY) Healthy
  │  │  └─ type: OUTPUT
  │  └─ beat/metrics-monitoring-metrics-monitoring-beats
  │     ├─ status: (HEALTHY) Healthy
  │     └─ type: INPUT
  ├─ endpoint-default

• elastic-agent status --output yaml

  
  info:
  id: 7c2067ff-30ff-4628-b8cf-af36fa56a524
  version: 8.12.0
  commit: 5cbf2e403c761f91d11eca6b9cb5385e0f07f2ce
  build_time: 2024-01-11 13:25:50 +0000 UTC
  snapshot: false
  pid: 1274
  state: 2
  message: Running
  components:

• id: beat/metrics-monitoring name: beat/metrics state: 2 message: 'Healthy: communicating with pid ''2343''' units:
  • unit_id: beat/metrics-monitoring unit_type: 1 state: 2 message: Healthy
  • unit_id: beat/metrics-monitoring-metrics-monitoring-beats unit_type: 0 state: 2 message: Healthy version_info: name: beat-v2-client version: 8.12.0 meta: build_time: 2024-01-10 21:09:16 +0000 UTC commit: 27c592782c25906c968a41f0a6d8b1955790c8c5

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[cmacknz]

for components using older versions of the protocol, the version_info.version.

I would just always report the build_hash and not try to deal with when version is missing.

If version is missing it must always match that of the running agent because of the way our release process works, so if we want to populate it you can just populate the agent package version.