Error-prone storage of throttled packet data

[shaspitz]

Problem

We currently store throttled slash and vsc matured packet data in the same chain-specific queue. These types are serialized by a byte enum. This is error prone.

Closing criteria

Improve how we serialize that data. See if there's any built-in protobuf metadata we can use to infer the type of value bytes that are being deserialized here

Problem details

This is related to #567, but that issue is focused on JSON ser/deser from IBC core, whereas this issue deals with how the packet data types are persisted in the provider store during the throttling process.

[shaspitz]

in ccv.proto there is a ConsumerPacketData type, introduced by #626. When this type starts getting used in throttling code, we should consider refactoring its name to not include "consumer"

Ie. it's confusing to be handling something that is "consumer data" in the provider store. Something like "packet data from consumer" would be easier to understand for quick readers

[danwt]

Related: we could refactor all our enums to start from iota + 1, this avoids us accidentally having an uninitiliased enum masquerade as the zeroth enum value

[shaspitz]

Implicitly closed by deleting all this shiz in #1102