ddb01f5355
I noticed CLN is sending our own channel update to us on reestablishment, we then assume it to be the remote nodes update and try to verify the signature against their pubkey which fails and throws `InvalidGossipMsg`. This adds a check preventing us from trying to save our own channel updates as remote update.