Add fallback method for RPC failures due to proto definition changes

[pharr117]

We have a consistent block failure at this transaction:

Block: 11093463
TX; 70107CA62C58B44D20BF8894666E1D149CEB0C429B027D519EB5BF45CF53F84A

The root cause of this one is that Osmosis changed the fields on the proto definition of one of their custom Proposal types. Due to this, the gov module cannot decode the TX during RPC requests and the RPC request fails.

See here for their removed field.

The solution for this one will be slightly complex because we will need to take into account:

1. The fact that the Node itself cannot decode the message
2. Our Lens codebase will not be able to decode the message either

[pharr117]

The exact error message is:

ERR Error getting transactions by block height (11093463). Err: rpc error: code = InvalidArgument desc = errUnknownField "*types.PoolRecord": {TagNum: 4, WireType:"bytes"}: tx parse error: invalid request. Will reattempt

[danbryan]

curious if can mintscan can decode it?