Ensure CometBFT v1 compatibility

[melekes]

• docs(cometbft): update ABCI links #116
• docs(cometbft): update ABCI and data structure links #117
• feat(rpc): add kvstore fixtures for v1 #118
• verify actual compatibility by migrating IBC upstream consumer crates
  • First stab at migrating to cometbft-rs informalsystems/ibc-rs#1103 (Migrate the codebase from tendermint-rs dependency to cometbft-rs informalsystems/ibc-rs#1073)
  • First stab at migrating to CometBFT-rs cosmos/ibc-proto-rs#190 (tendermint proto imports are not consistent between cosmos-sdk and ibc-rs revisions cosmos/ibc-proto-rs#194, Migrate from tendermint-proto to cometbft-proto dependency cosmos/ibc-proto-rs#189)
  • Migrate from tendermint-rs to cometbft-rs informalsystems/hermes#3865 (Adapt to cometbft-rs informalsystems/hermes#3820)

[kamiyaa]

Will this introduce a new variant to EventAttribute ? ie. EventAttribute::V1

[melekes]

Will this introduce a new variant to EventAttribute ? ie. EventAttribute::V1

cometbft-rs/cometbft/src/abci/event.rs

Lines 41 to 47 in ac3db79

	pub enum EventAttribute {
	/// EventAttribute keys and values in TM37 and later are plain strings.
	V037(v0_37::EventAttribute),
	/// EventAttribute keys and values in TM34 are base64-encoded strings.
	V034(v0_34::EventAttribute),
	}

Do we need a V1?