Use updated ICS23 proof spec supporting noninclusion proofs

[hdevalence]

Is your feature request related to a problem? Please describe.

Now that we've been able to merge our extensions to ICS23 upstream, we should ensure that we ship a version of Penumbra that uses the correct ICS23 proof spec. This is important to do as part of the next testnet release, because otherwise, we'll have testnet and testnet-preview using different proof specs, and the relayer doesn't know how to support that (and shouldn't need to, because there should just be one correct proof spec).

Describe the solution you'd like

Getting this done has a somewhat deep dependency chain, so we should focus to make sure we get all of the steps done in time:

• Ensure that the published jmt crate uses ics23 = "0.10" and has the correct proof spec
• Use the updated jmt crate, partially done in storage: integration of jmt@0.4.0 & reverse index for jmt key hashes #2032 ...
  • but blocked on [WIP] Upgrade to ibc 0.37 #2374, which is impossible ...
  • so we need the first part of Tracking issue: IBC Rescue Plan #2379 instead:
    • Finish and merge ics20: complete bridge (implement recv_packet_execute) #2392
    • Update the IBC component in penumbra_app to use ibc-types 0.1.0. #2380
    • Update all fields on domain types to be pub ibc-types#2
    • Vendor ibc-types methods into the IBC component. #2381
    • Update to use the latest ibc-proto and ics23 crates ibc-types#3

[conorsch]

Discussed with the group today, and added the WIP PR #2392 as an early blocker. Once that lands, we can focus on the other tasks. Given team schedule, it's likely to be @avahowell and @erwanor driving this work to completion today and tomorrow.

[hdevalence]

For some reason I thought that ibc-proto 0.30.0 included the ICS23 changes already, but that's not the case: penumbra-zone/ibc-types#3 (comment)

So this is blocked on those two crate releases. Let's see how things go on Monday; one possibility is that we can consume them, possibly delaying the release a day or two; another is that we stick to the schedule and let the ICS23 changes slip.

[erwanor]

@hdevalence a third, more sinister, option is to fork ibc-proto-rs with the right vendored ics23 protogen'd: https://github.com/penumbra-zone/ibc-proto-rs/tree/vendor_ics23 and plug back into upstream for testnet 52.

[hdevalence]

Sure, that's a good thing to consider as a temporary measure -- we should definitely avoid a long-term fork of those crates, though.

[hdevalence]

I copied the branch that is supposed to be merged and fix our problem into our repo: https://github.com/penumbra-zone/ibc-proto-rs/tree/penumbra

[erwanor]

@hdevalence thanks, i'll use it to get ahead of the monday release.

[hdevalence]

I'm working on an update to ibc-types at the moment.

[erwanor]

Moved to testnet 53, as a result of #2032 getting delayed.

[redshiftzero]

Will be closed by #2628