Improve Device Audit Log Events

[joepavitt]

Description

Last step for #4873 (comment)

With the new version history view, we are lacking a lot of clarity at the Device-level whereby we only have Application-level events. This task track the addition of the following events:

• Event: Deploying to Remote Instance via a Pipeline

  • Existing audit event: application.device.snapshot.device-target-set or team.device.updated

• Event: Deploying through an Instance

  • Existing audit event: project.snapshot.device-target-set

• Event: Snapshot Rollback

  • Existing audit event: team.device.updated or application.device.snapshot.device-target-set

• Event: Snapshot Create

  • Existing audit event: application.device.snapshot.created

See the initial discussion here

We need to settle on appropriate audit event labelling for the device-level events for each element here.

Epic/Story

No response

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

PR's

Preview Give feedback

1. Add a device.pipeline.deployed event to track device state changes from the device perspective #5149
   +0
   
2. remove the device.pipeline.deployed event from the team audit log to prevent duplication
3. Display the version history tab to instance owned devices #5153
   +0
   
4. Show empty state message for unassigned devices snapshots page #5157
   +0
   
5. Add a device.project.deployed event to track device state changes from the device perspective #5155
   +0
   
6. Update Changelog

[cstns]

Event: Snapshot Rollback

Existing audit event: team.device.updated or application.device.snapshot.device-target-set

In this case we can't really deduce if the instance was rolled back or forward. I'll generalize it into a snapshot deployed event