Channel handling: have a dedicated event topic per event key

[Lance-Drane]

Currently, the events channel looks like this:

<organization>/<facility>/<system>/<subsystem>/<service>/events

This publishes all events to a single channel, which has some problems regarding authorization (plus requiring clients to perform excessive control flow branching).

A better approach may be:

<organization>/<facility>/<system>/<subsystem>/<service>/events/<event_name>

where event_name represents an event key.

[Lance-Drane]

This ended up getting resolved in 1460e98

This was important to tackle alongside #23, the actual channel handling logic is now:

<organization>/<facility>/<system>/<subsystem>/<service>/events/<capability_name>/<event_name>