check_misbehaviour_and_update_state(): commit verification might use the wrong chainId

[plafer]

In ibc-go, the chainID's revision_number is substituted with the header's revision_number before validator set commit verification (here). Our current implementation does not do that (here).

[plafer]

Curiously, we make the substitution before ensuring that chain id match here. I am not sure if this is equivalent (i.e. if our chainID does not match both headers' chain IDs, then the commit verification would fail)