Remove height from ConsensusState in ICS 007 implementation

[cwgoes]

Storing the height in the value is redundant, because consensus states are always stored under a key which includes the height.

I think the only place we use this is here but it should be easy to pass the height through.

Ref https://github.com/cosmos/ics/issues/456

[colin-axner]

should we do this for solo machines as well in order to remove the GetHeight interface function? That would just mean moving the (latest) sequence to client state

[cwgoes]

Yes, that's fine I think.

[colin-axner]

I think the only place we use this is here but it should be easy to pass the height through.

I'm honestly confused why this check is needed. It seems to me in all cases of its usage, the consensus state.Height checked was retrieved using the header.Height being checked against. The only time this check would fail is if for some reason we had been storing a different height in the consensus state than the one used for lookup. Maybe I am missing something?

[cwgoes]

It seems to me in all cases of its usage, the consensus state.Height checked was retrieved using the header.Height being checked against.

If that's true, we can remove it.

The only time this check would fail is if for some reason we had been storing a different height in the consensus state than the one used for lookup.

Are we still storing duplicate data here? Presumably this PR will fix that.