Use custom JSON value type with Rc inside. It cannot be edited, but producing new values based on child element is very cheap.
This new type is used exclusively in AquaVM internals. Interface APIs use serde_json's Value or JSON strings, as before.
---------
Co-authored-by: raftedproc <71657594+raftedproc@users.noreply.github.com>
* feat(execution-engine)!: canon stream map support [fixes VM-301]
Canon stream map is a CRDT-like map structure that contains a
canonicalized stream map and allows indexed access to its
contents. ATM CSM supports both strings and int64 keys.
Refactored stream and stream generation a lot, it introduces the following changes:
- no generation in data anymore, AquaVM relies on generation inside data to stay valid and places value accordingly to it
- stream is internally divided into previous, current, and new values, before, it was one array for all of them
- recursive streams cursors are refactored and rely on new generation values instead
- the Generation enum was refactored and now contains the source of the generation
* `ValueAggregate` refactoring
0. Service results, canon results and literals are constructed as
separate types that are further wrapped with `ValueAggregate`.
1. `ValueAggregate` is enum that contains all the provenance info.
2. Construction methods get provenance information as well.
* Rename CID state field
Prepare to adding a canon CID field: rename `canon_tracker`/`canon_store`
to `canon_element_tracker`/`canon_element_store`.
* Add canon result store/tracker
* Rename some structs that have CIDs inside
Reflect explicitly that they contain CIDs inside:
`CanonResultAggregate` -> `CanonResultCidAggregate`
`ServiceResultAggregate` -> `ServiceResultCidAggregate`
---------
Co-authored-by: Mike Voronov <michail.vms@gmail.com>