Port default behavior and replication behavior is not correct

In this PR we created new message for updating node values such as "UsingDefaultValue" and "ArgumentLacing". Also in this PR we implement ability to send information about port default value to the Flood.
@pboyer , thanks for pointing that :) I've reviewed code in this section and realised that throwing exception is redundant, because we use reflection to obtain node name and then search for the node using name, received earlier.