Implement a new approach to communicating serialised Realm objects between device and plugin

[gagik]

The current approach for sending over Realm object information between the plugin and the device has variety of issues.

A new implementation should likely address multiple existing issues at once. Based on the summary of previous issues, here are some possible considerations for the new implementation:

1. Wrap serialised Realm Objects with parent objects that store i.e. _pluginObjectKey rather than introduce those fields to the serialised object itself (as described by Special property names #86 and fixes Object Key in data inspector #93)
2. In the wrapper of the serialised object being sent over to the plugin (or other place that may make more sense), include information that can be used to derive types of i.e. mixed fields. (fixes Type erasure and support for mixed #84)
3. When sending an object that has a linked object, it would be enough to send the objectKey (and primaryKey if present). The primaryKey could be used to nicely render the linked objects in the table. (fixes Flattening of linked objects #85).
4. Do not attempt to query embedded objects (fixes Embedded Object Support #113)
5. Use latest toJSON serialiser to avoid circular dependency issues (fixes Circular references #96). With new toJSON implementation from Improve toJSON functionality and remove JSONSerializerReplacer realm-js#4997, it should now be easier to represent and serialize Realm objects as plain JavaScript objects which will hopefully ease some complexity.