[FEATURE] Tuple decoding with components

[Stevengre]

• feat(rt): handle zero-sized locals #809 provided the first step for decoding tuple, but we should support tuple decoding as soon as possible.

Here's thought from @jberthold

It depends on how the layout is, maybe we can just decode the components in sequence? Or can the fields be out of order for tuples?