tremor binary encoding

[Licenser]

Describe the problem you are trying to solve

For networking and storage, it would be good to have a stable binary representation of tremor value. This might also enable (or at least make it more feasible) to pass data in and out of environments such as WASM runtimes.

Describe the solution you'd like

There is no clear solution here yet since this is a topic that requires a RFC, that said there are some requirements:

1. the encoding needs to be binary stable under equivalence (meaning that something like {"a": 1, "b": 2} and {"b": 2, "a": 1} need to encode to the same binary value.
2. It should be fast (yea that's somewhat of a given 😂)
3. It needs to support versioning (since we will evolve it might matter to be able to detect what version it comes from)
4. It needs to be architecturally independent (big vs little-endian encoding)
5. It is worth considering our primary use-case and optimizing for it (I.e. map keys are usually small etc.)

Notes

This is a large, long-running issue and might evolve into a in-memory format for tremor value that allows more then just storage (as that would make decoding really cheap) - not something needed from day one but it is worth keeping the option in mind