Use 8 bytes to hash UpgradeConfig

8 bytes is generally enough to fingerprint the UpgradeConfig changes, so nodes
can exchange the hash as part of the handshake[1]

[1] https://stackoverflow.com/questions/18134627/how-much-of-a-git-sha-is-generally-considered-necessary-to-uniquely-identify-a

Author: nytzuga

plugin/evm/message/handshake/upgrade_config.go

@@ -111,6 +111,9 @@ func (r *UpgradeConfig) Bytes() []byte {
 	return r.bytes
 }
 
-func (r *UpgradeConfig) Hash() [32]byte {
-	return sha256.Sum256(r.bytes)
+func (r *UpgradeConfig) Hash() [8]byte {
+	hash := sha256.Sum256(r.bytes)
+	var firstBytes [8]byte
+	copy(firstBytes[:], hash[:8])
+	return firstBytes
 }