List hosts API: populate users and labels

[noahtalerman]

Goal

User story
As an IT admin who exports host data from Fleet data into my asset management tool (ex. ServiceNow),
I want to populate user and label data in the GET /hosts API endpoint
so that I can insert this info into the host records in my asset management tool.

Objective

Customer promises + renewal requests

Original request

• 20795

Context

• Product designer: @rachaelshaw

Changes

Product

• [x] UI changes: N/A
• [x] CLI (fleetctl) usage changes: N/A
• [x] YAML changes: N/A
• [x] REST API changes: Docs PR
• [x] Fleet's agent (fleetd) changes: N/A
• [x] Activity changes: N/A
• [x] Permissions changes: N/A
• [x] Changes to paid features or tiers: N/A
• [x] Other reference documentation changes: N/A
• [ ] Once shipped, requester has been notified

Engineering

• [ ] Feature guide changes: Check if there is an existing guide to update
• [x] Database schema migrations: no need
• [ ] Load testing: To be considered as part of the test plan.
• [ ] Backend - implement the API change as in the above PR
• [ ] Test-plan - To be created by the DRI engineer and approved by QA person

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. [ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
2. [ ] QA (@____): Added comment to user story confirming successful completion of QA.

[sharon-fdm]

Hey team! Please add your planning poker estimate with Zenhub @getvictor @lucasmrod @mostlikelee

[sharon-fdm]

Please add your planning poker estimate with Zenhub @iansltx

[noahtalerman]

Hey @zayhanlon heads up, this user story didn't make it into the upcoming engineering sprint due to capacity.

It's still prioritized. We left it on the drafting board so that it can be pulled into the next engineering sprint.