Communicate all FBP runtime messages to coordinator

[jonnor]

We now have a queue/exchange pair (sending, receiving) for communicating FBP protocol messages, from a single participant to coordinator. But currently only trace commands are handled. Instead all FBP runtime messages should be forwarded. This requires loading the graph with runtime.MsgFloRuntime instead of using noflo.ComponentLoader like we do now.

Needed to allow full nested access to NoFlo runtimes running inside/behind a MsgFlo runtime.

The queue names used for this purpose should be put in the MsgFlo participant discovery messages.

[jonnor]

There are a couple of things needed here:

• [ ] Instantiate Runtime and use it for communicating FBP messages
• [ ] Declare the queues used in MsgFlo discovery message
• [ ] Move FBP tracing subprotocol support into noflo/noflo-runtime-base#36
• [ ] Find a way with Runtime to load/mount components (not just graphs). Current thinking: Synthesize a graph of one component including exports in/outports
• [ ] Find a way with Runtime to load/mount graphs by name instead of filepath. Hack: Use the same kind of graph synthesis as for component. Or maybe can use ComponentLoader to resolve the path to the graph? Alt: Don't use the defaultGraph functionality in -base, instead replicate what it is doing with own loaded Network.
• [ ] Find and implement passing received data in/out of NoFlo network and MsgFlo queues