fix: incorrect and inadequate checks of sync message

[yangby-cryptape]

What problem does this PR solve?

The checks of sync message are incorrect and inadequate since CKB2021.

ckb/sync/src/synchronizer/mod.rs

Lines 718 to 733 in 5dadcbf

	if let packed::SyncMessageUnionReader::SendBlock(ref reader) = item {
	if reader.count_extra_fields() > 1 {
	info!(
	"Peer {} sends us a malformed message: \
	too many fields in SendBlock",
	peer_index
	);
	nc.ban_peer(
	peer_index,
	BAD_MESSAGE_BAN_TIME,
	String::from(
	"send us a malformed message: \
	too many fields in SendBlock",
	),
	);
	return;

• SendBlock is the same before and after CKB2021, so the result of checks is always be true.

  ckb/util/gen-types/schemas/extensions.mol

  Lines 264 to 266 in 5dadcbf

  	table SendBlock {
  	block: Block,
  	}

• The Block could have 1 more field after CKB2021.

  ckb/util/gen-types/schemas/blockchain.mol

  Lines 94 to 99 in 5dadcbf

  	table Block {
  	header: Header,
  	uncles: UncleBlockVec,
  	transactions: TransactionVec,
  	proposals: ProposalShortIdVec,
  	}

  ckb/util/gen-types/schemas/blockchain.mol

  Lines 101 to 107 in 5dadcbf

  	table BlockV1 {
  	header: Header,
  	uncles: UncleBlockVec,
  	transactions: TransactionVec,
  	proposals: ProposalShortIdVec,
  	extension: Bytes,
  	}

• As a comparison, the checks of relay message are correct.

  ckb/sync/src/relayer/mod.rs

  Lines 780 to 781 in 5dadcbf

  	if let packed::RelayMessageUnionReader::CompactBlock(ref reader) = item {
  	if reader.count_extra_fields() > 1 {

  ckb/util/gen-types/schemas/extensions.mol

  Lines 138 to 153 in 5dadcbf

  	table CompactBlock {
  	header: Header,
  	short_ids: ProposalShortIdVec,
  	prefilled_transactions: IndexTransactionVec,
  	uncles: Byte32Vec,
  	proposals: ProposalShortIdVec,
  	}
  	table CompactBlockV1 {
  	header: Header,
  	short_ids: ProposalShortIdVec,
  	prefilled_transactions: IndexTransactionVec,
  	uncles: Byte32Vec,
  	proposals: ProposalShortIdVec,
  	extension: Bytes,
  	}

Check List

Tests

• Unit test
• Integration test

Release note

Title Only: Include only the PR title in the release note.