Currently, netconf in honeycomb needs a DataBroker, where it stores its state data. This is very small amount of operational data, so there's no need to dedicate:

• config in memory data store instance
• operational in memory data store instance
• InmemoryDOMDataBroker instance

This is too heavyweight and should be toned down with e.g. (DataTree + ReadableManager + Honeycomb's DOMDataBroker implementation) or (just store it in context) to reduce the amount of threads in use and the overall footprint.

We could use Context data broker for netconf as well, however netconf uses data change notifications, which are not supported by DOMDataBroker used in context pipeline.