Implement check_for_misbehavior for ethereum light client header #561
Description
Description
With the introduction of historical updates in #503, it is now possible for a validated header to be considered a misbehavior proof if a historical update successfully updates the light client to a different state.
Therefore, the light client must be frozen if this occurs, and this logic should be implemented in the already existing check_for_misbehavior which is called by ibc-go after the verify client message is called