The monitor-events command only monitors default events

The `monitor-events` command monitors the default "events" endpoint of an IoT Hub; therefore, after adding routing to send some messages to other endpoints, a developer loses all visibility into those messages.
'monitor-events' should monitor messages before they are routed. This functionality could be configurable. Ideally CLI output would include an additional field indicating the route(s) that it matched.

Start by locating the monitor-events command and reading how it currently consumes the default events endpoint. Investigate where pre-routing messages can be observed and how routing matches are exposed, then define the configurable behavior and CLI output needed; done means messages sent to alternate endpoints remain visible and matched routes are reported when enabled.

Written by the indexing model from the issue text.