Reduce redundant validation calls

[MatheusFranco99]

Drop redundant calls

SignedMessage.Validate() is called multiple times for the same message, as pointed by #326. This PR aims to solve this duplication.

The current flow is shown below.

Notice that isValidProposal calls validRoundChangeForData and validSignedPrepareForHeightRoundAndRoot due to the justification messages.

If we want to keep the higher level validation calls we could get the following

The problem is that the Prepare and Round-Change messages would still do double validation. And the checks can't be dropped due to the isValidProposal function.

If we were to keep the lower level calls, we would get

This produces no duplicated calls but, from a design point of view, it's bad to do a light validation check late.

Another option is to change the Validation function to also validate nested messages (which I think is best), as below.

---

Closes #326.

[MatheusFranco99]

@GalRogozinski @y0sher @olegshmuelov @moshe-blox
I would like to know your opinion on this issue before I start the changes. The PR description explains the options.

[y0sher]

@MatheusFranco99 I agree with you on this that last option is the best. I think another option exists where we only validate the top message. but then when we call Validate on underlying message we are only validating the underlying message.
I think the point is not to validate same data more than once. but also a nice to have property is that we do not validate data that we don't need to.
for example if we deem the message as bad and not go forward after first validate and some other checks, in the last option you mentioned we might be validating internal messages without needing to.

[GalRogozinski]

Is there some overlap with #358 ?

[MatheusFranco99]

Perhaps, there's overlap but their goals are a bit different. Here the goal is not to verify messages already verified (in proposal construction). In #358 , the goal was to avoid calling SignedSSVmessage.Validate() many times when processing a message