Update activity feed

[gillespi314]

Goal

User story
As an IT admin,
I want to have a detailed activity feed
so that I can keep track of who changed what and build automations using the activity webhook.

Objective

Mission critical MDM replacement

Original requests

This story covers the following requests:

• Add software ID to add/edit software activity payload (customer request Add software ID to add/edit software activity payload #22063)
  • Highest priority for deebradel
• Add activity for editing the "Install software" policy automation (Policy automations: install software #19551)
• Add activity for editing the "Run scripts" policy automation (no issue)
• Host activity feed: SCEP certificate delivery #22538
• As part of this story we want to clarify the actor: tell the user when Fleet is triggering software/script runs (automatic) v. IT admin triggering (manual) v. end user triggering (manual)
• In the current iteration, Fleet always shows the user who added software/script as the actor in the activity feed
  • Related: Cut from Install software and run setup script when Macs boot #19372 and moved to this ticket. (Relevant designs)

Context

• Product designer: @marko-lisica

Changes

Product

• Reference documentation changes: Covered by activity changes below.
• UI changes: Figma link
• CLI usage changes: No CLI changes.
• REST API changes: Covered by activity changes below.
• Fleet's agent (fleetd) changes: No fleetd changes.
• Activity changes: Activity changes: Update activity feed #22573
• Permissions changes: Already covered by permissions guide ("View all activity" row).
• Changes to paid features or tiers: Available for Fleet Free and Premium.

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.

[gillespi314]

Following up on #21640:

I think we don't have an activity for ABM currently. It makes sense to me to update enabled_vpp & disabled_vpp that we already have (add location under details) and we file follow up story to tackle ABM and possibly if we want to track when user change VPP teams and ABM teams.

[noahtalerman]

Thanks for tracking this one @gillespi314!

Auditability is core to Fleet. We'll weight this one at the next feature fest.