Hooks

The output from /api/collections/hooks shouldn't contain the name of the event since there are two layers of indirection between a hook and an event, via hook-type. A hook-type can handle multiple events.

I agree though that `event` (e.g. `node-booted`) should be included in the event's entry. I'll add that. Maybe `cause` would be a good way to avoid the now-ambiguous `event` identifier.

For the base question of "When I booted nodeXYZ, what hooks were triggered and how did they do ?", I envision this would be answered via `razor nodes nodeXYZ log` then looking at entries that say 'cause = node-booted'. To that effect, we might considering having `cause` be its own field for easier viewing/future filtering.