[Fleet] Add Host.ID to the Agent overview.

[WiegerElastic]

Describe the feature:

Nothing earth shattering here, just a minor QoL improvement for operators: Add the host.id information to the Agent overview page. The information is collected by Agent already I believe.

Describe a specific use case for the feature: Some asset management tools (like Jamf) have a hard time digesting the output of host.name or they don't allow you to search for agent.id because the tool doesn't know the data exists/collects the data. Host.id can often be used as an alternative here.

Let's take Jamf as an example. I need to lookup a machine that's reporting with host.name daves-macbook-pro-local, with agent ID cf82792e-d26a-4723-8b95-8d240ea50702 and Based on the current Agent overview, I have a couple of options I can use to search Jamf:

• Host.name: there are 2 issues with this:

  1. Not all companies enforce unique hostnames. For example, there might be 20+ folks called "Dave" that have a MacBook. That's potentially 20+ "Dave Macbook Pro" machines. So this still requires a lot of work on my end to find the correct user/machine.
  2. Jamf doesn't accept output formatted as daves-macbook-pro-local so I need to reformat it (and have to guess a bit which format it will accept) and will probably still get a lot of hits based on this hostname.

• Agent.id: Jamf doesn't collect this data so I'm not able to search for it. If there's an Agent reinstall happening, it might generate a new Agent ID for this machine, making it harder to track the machine over time (at least visually).

Host.id seems to be generated of the machine's UUID. I can search for that output in Jamf and I can be fairly certain that the data remains stable over time.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)