Policy automations > Install software: improve empty state

[noahtalerman]

Goal

User story
As an IT admin,
I want to know what software can be installed
so that I'm not confused if I see an empty list or some software is missing in policy automation > install software modal.

Objective

Small UX improvement

Original requests

• Improve empty state for policy automation: install software #23182

Context

• Product designer: @marko-lisica

Changes

Product

• UI changes: Figma link
• CLI (fleetctl) usage changes: No changes.
• YAML changes: No changes.
• REST API changes: No changes.
• Fleet's agent (fleetd) changes: No changes.
• Activity changes: No changes.
• Permissions changes: No changes.
• Changes to paid features or tiers: Available in Fleet Premium.
• Other reference documentation changes: No changes.
• Once shipped, requester has been notified

Engineering

• Feature guide changes: TODO
• Database schema migrations: TODO
• Load testing: TODO

ℹ️  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.

[marko-lisica]

We decided to close this one since we'll work on this story #23115 in next sprint.

TODO @marko-lisica : document this in https://fleetdm.com/guides/automatic-software-install-in-fleet

[fleet-release]

In clouds of software,
Clear lists guide the IT gaze,
Confusion fades away.