There have been cases where either:

1. Auto-start/Auto-stop triggers a start/stop
2. An admin user triggers a start/stop

And it's unclear why a workspace transitioned state. I used this opaqueness to troll Kyle for multiple days.

I suggest we add an "Actor" Initiated By column to the Timeline table in the Workspace page and an Actor field on the Build Log page.

Implementation notes:

We should add a system user here to report in the logs for what user is taking what actions.

AC

Show a human readable name for the initiator ID for all builds.
Add another column in the build logs for initiator
Testing: storybook for UI, human readable name, check that the name appears on the page, unit test for API returning human readable name