actions status does not reference the action that was triggered

[Richard Harding]

When running an action I can trigger many and the show-action-status does not help me identify what the action was after the fact.

Current behavior:

  juju run-action percona-cluster/0 pause
  Action queued with id: 8881ff73-f225-4fe9-8c56-fc171d8b5e68
  juju run-action percona-cluster/0 backup
  Action queued with id: a62a9385-05c7-4342-883d-ac2dd59dfad8
  juju run-action percona-cluster/0 resume
  Action queued with id: 780381ce-8500-4526-8b45-e7f95ea1e26a
  juju run-action percona-cluster/0 backup
  Action queued with id: 8f8aee46-4e5f-421b-80ef-e51066d92e79

  juju show-action-status
  actions:
  - id: 780381ce-8500-4526-8b45-e7f95ea1e26a
    status: completed
    unit: percona-cluster/0
  - id: 8881ff73-f225-4fe9-8c56-fc171d8b5e68
    status: completed
    unit: percona-cluster/0
  - id: 8f8aee46-4e5f-421b-80ef-e51066d92e79
    status: completed
    unit: percona-cluster/0
  - id: a62a9385-05c7-4342-883d-ac2dd59dfad8
    status: failed
    unit: percona-cluster/0

There should be some information on the action that triggered it for context.

  juju show-action-status
  8881ff73-f225-4fe9-8c56-fc171d8b5e68
    action: pause
    arguments:
    status: completed
    unit: percona-cluster/0
    completed at: 2016-06-28 12:32:00
  a62a9385-05c7-4342-883d-ac2dd59dfad8
    action: backup
    arguments:
    status: failed
    unit: percona-cluster/0
    completed at: 2016-06-28 12:32:30
  780381ce-8500-4526-8b45-e7f95ea1e26a
    action: resume
    arguments:
    status: completed
    unit: percona-cluster/0
    completed at: 2016-06-28 12:34:03
  8f8aee46-4e5f-421b-80ef-e51066d92e79
    action: backup
    arguments:
    status: completed
    unit: percona-cluster/0
    completed at: 2016-06-28 12:35:15

Notes:
The order of the items is kept by their completion times. Here is a very specific case where order is important. I tried to backup after I stopped the database. Ooops!

We've added the action that was run and the arguments used with it.

the completed at timestamp is tracked to help identify timelines that might tie into things like audit logs that would have effected if the action completed successfully or not.

We don't prefix the whole thing with actions: key as there's no point to it here.