Fix incorrect ordering in PendingAttestation, Attestation, Eth1Data

[0xMushow]

This incorrect ordering was confusing and can cause clients to implement wrongly the following functions.

According to the structure in the specifications

data should be the 2nd parameter:

consensus-specs/specs/phase0/beacon-chain.md

Lines 426 to 430 in c20c1bd

	class PendingAttestation(Container):
	aggregation_bits: Bitlist[MAX_VALIDATORS_PER_COMMITTEE]
	data: AttestationData
	inclusion_delay: Slot
	proposer_index: ValidatorIndex

committee_bits should be the 4th parameter:

consensus-specs/specs/electra/beacon-chain.md

Lines 351 to 357 in c20c1bd

	class Attestation(Container):
	# [Modified in Electra:EIP7549]
	aggregation_bits: Bitlist[MAX_VALIDATORS_PER_COMMITTEE * MAX_COMMITTEES_PER_SLOT]
	data: AttestationData
	signature: BLSSignature
	# [New in Electra:EIP7549]
	committee_bits: Bitvector[MAX_COMMITTEES_PER_SLOT]

deposit_count comes first prior to block_hash.

consensus-specs/specs/phase0/beacon-chain.md

Lines 436 to 439 in c20c1bd

	class Eth1Data(Container):
	deposit_root: Root
	deposit_count: uint64
	block_hash: Hash32

[jtraglia]

LGTM, I like little improvements like this 🙂 thank you!