Allow optional field in node-to-node and client-to-node

As of now the validation schema for all messages is strict and doesn't allow new (optional) fields to be included at the end.

As a long-term we should consider using protocolVersion, but for now it should be enough just to allow new (unknown) fields, so that old nodes don't break.