Server-side Chromium stream bug workaround.
Client-side Chromium workarounds and fixage.
Only set allow editing once both network & floorplan states ready.
Handle node addrs transparently in client side, change notification order.

Drop the forcing of node addresses in the client side code to be an int,
it can now also be a string (e.g. an IP) and the client-side should just
always use the same type as it received.

Also only call notifiers on state changes after updating the state, so
that the notifiers can safely query new state (if needed.. shouldn't be
needed anyway).
Allow full use of channels that have no value, but were discovered.

This happens before a channel has been queried for specific value,
and for publish channels also before any publish message was received
from that channel.
Ensure floorplan is not saved if it couldn't be loaded.

This could cause someone to wipe out a nice floorplan.
Enable messages from the Discovery Agent.

Also make sure incoming messages are logged before being processed
by the state tracker so that if the state tracker actions lead to
generation of an outgoing message, the logging happens in order.