Add: Checksum check on decoder

[RaulTrombin]

Actually, the checksum isn't checked on the decoder itself;
it's only verified when you attempt to build a ProtocolMessage from it.
PR propose validating it upon receipt and returning an error promptly.

[joaoantoniocardoso]

A question -- do we want to prohibit access to the message when the CRC is wrong, or do we want to allow the user to access it even if the CRC is wrong?

[patrickelectric]

A question -- do we want to prohibit access to the message when the CRC is wrong, or do we want to allow the user to access it even if the CRC is wrong?

I think that would be better for us return the message inside the error enum

[RaulTrombin]

A question -- do we want to prohibit access to the message when the CRC is wrong, or do we want to allow the user to access it even if the CRC is wrong?

I think that would be better for us return the message inside the error enum

@joaoantoniocardoso humm, then would be possible try to recover the msg,
we can do something like @patrickelectric suggested, should I modify this PR for it?

[patrickelectric]

A question -- do we want to prohibit access to the message when the CRC is wrong, or do we want to allow the user to access it even if the CRC is wrong?

I think that would be better for us return the message inside the error enum

@joaoantoniocardoso humm, then would be possible try to recover the msg, we can do something like @patrickelectric suggested, should I modify this PR for it?

You only need to update ChecksumError declaration

[RaulTrombin]

@joaoantoniocardoso thks for input.
Modief ParseError::CheksumError to contain ProtocolMessage as Success does.