Improve communication of serialised Realm objects between device and plugin

[gagik]

This PR...

• Wraps serialised Realm Objects instead of introducing new fields (closes Special property names #86 and Object Key in data inspector #93)
• Linked objects are now lazy-loaded, they will display their object key (just for internal reference) and their actual values can be seen when inspected. (closes Flattening of linked objects #85).
• Uses flatted.toJSON and the circular reference-safe realmObject.toJSON() from v11 to send objects (closes Circular references #96)
• Adds embedded object support (closes Embedded Object Support #113)
• Adds shared type definitions across the plugin and desktop.

TODO:

• Empty collections being sent over not handled correctly
• Embedded object modification not handled correctly
• Test modification of different types
• Test expanding data

[takameyer]

Really happy about all the work you've put into this. Looks like the flipper plugin is now useable!
My only suggestion is to consider breaking up "common" and "shared" and getting some of those types closer to the component using them. But this could be done later, just wanted to provide something to think about.
LGTM 🚢

[takameyer]

Did you want to address this in a separate PR, or is this doable now?

[gagik]

I was thinking of separate PR. although I just thought of a way to make this simpler, i.e. just send over primaryKey if it exists along with objectType / objectKey for references, so I might just do this. I generally avoid leaving TODOs like this but because of the state of the code right now this seemed like the quickest way to leave some bits for future planning.