Expose ClientPort communication warning callback for protocol/schema mismatch reporting

[azisislm]

No description provided.

[ryan-the-crayon]

Let's do this. In the case that a onCommunicationWarning callback is set, no need to log the warning above.

[ryan-the-crayon]

So there is one thing that is annoying. Unfortunately, now communications warnings will be emitted even for cases that doesn't really indicate a protocol breakage. For example, if received a message for a channel that was recently closed can also emit a communication warning.

I think what we need is to add a "kind" field to the communication warnings to indicate the type of warning. For example: rpcParameterTypeError, channelUnknown. We will also need to add this field to the underlying transport level protocol. This field will have to be optional to prevent breakage. Also, when parsing this kind, it should map unknown values to "unknown" to provide backwards compatibility. This way, upper level users can use this "kind" field to determine the severity of the issue.