ibc-types: bump prost, tendermint, ibc-proto, ics23

[SuperFluffy]

Updates the following dependencies:

• ibc-proto: 0.42.2 -> 0.51.1
• ics23: 0.11.3 -> 0.12.0
• prost: 0.12.0 -> 0.13.3
• tendermint: 0.34.0 -> 0.40.0
• tendermint-light-client-verifier: 0.34.0 -> 0.40.0
• tendermint-proto: 0.34.0 -> 0.40.0
• tendermint-rpc: 0.34.0 -> 0.40.0
• tendermint-testgen: 0.34.0 -> 0.40.0

The bump to the latest tendermint version required bumping prost, which in turns required updates of ibc-proto and ics23 (where I opted for their latest releases, respectively).

The two larger changes are:

1. From tendermint@v0.40.0 onward conversions between core::time::Duration and protobuf.google.Duration are now fallible. I introduced a newtype wrapper CometBftDuration to restore the previous behavior saturating at i64::MAX (for seconds) and i32::MAX (for nanos), respectively.
2. From tendermint@v0.36.0 onward tendermint::abci::EventAttribute became an enum with variants V037 and V034, and introduced the fallible accessors EventAttribute::key_str and EventAttribute::value_str, in addition to the infallible EventAttribute::key_bytes and EventAttribute::value_bytes. This required changes in many TryFrom<Event> impls that would previously match on &str keys and directly move (or parse) String values. I chose to avoid extra error handling, instead matching on byte-string using value_bytes() (e.g. now b"packet_src_channel" => {} instead of the previous "packet_src_channel" => {}), and relying on String::from_utf8_lossy for the values.

[erwanor]

ACK. This makes sense to me. This is a domain type change, but doesn't affect the wire protocol.