Support compat addresses for ibc-in

[grod220]

Closes #1053

For noble, we need to encode our addresses to bech32 (not bech32m). In core, we have a special prefix for this specific case: https://github.com/penumbra-zone/penumbra/blob/main/crates/proto/src/serializers/bech32str.rs#L146.

Amended our bech32m package to support this new encoding method.

[Valentine1898]

How long will the ibc transfer from noble take?
I sent a transaction, but my balance in noble has changed only by the value of the fee 🤔

[grod220]

Currently the client state has expired. We'll need to work with the protocol team in getting these back up before we get a successful transfer. However, after this PR, we are no longer getting the bech32 error like we had before. Thanks for testing though!

[turbocrime]

rename to just penumbracompat.ts to match other files in this dir

[grod220]

But aren't these files named according to the prefix? For some reason, this prefix uniquely has the 1 in it: https://github.com/penumbra-zone/penumbra/blob/d13d731fadd665d7f2ec38c3bde57f53b2e86891/crates/proto/src/serializers/bech32str.rs#L146

[grod220]

I also wonder if it has this number in it because we may need to have penumbracompat2 for some other chain in the future.

[turbocrime]

interesting. 1 is a valid prefix character, but it is also the separator character, and this may be a bug in core or has some unexplained meaning like version as you suggest.

i can't find any examples or documentation on this.

cc @avahowell you committed the penumbracompat1 in core?

[turbocrime]

suggestions in #1083