Investigate ProtoBuf and Streaming to improve graphic serialization

[TimPurdum]

We have discussed many ways of improving the serialization and loading of large data sets

• Use Protobuf serialization instead of JSON (smaller, faster)
• Use DotNetStreamReference to pass data as a stream to JavaScript, and read graphics as they come in
• Somehow gain access to the shared memory space between WASM and JS (for wasm only), and pass a pointer to the data
• Combine several of the above, and abstract so that Blazor Server, WASM, and MAUI all work efficiently with the current API methods

[TimPurdum]

The main sticking point for all of the solutions above is that they do not support the blazor ObjectReference system. You cannot, without significant hacking, pass DotNetObjectReference to JS or JSObjectReference to C# via any of the systems except the built-in JSON serialization in IJSRuntime. This means that, in order to track and update graphics, we would have to

1. fall back to our own custom registration dictionary and rewrite all the update calls like SetGeometry (again).
   OR
2. have a separate callback to .NET that registers the JSObjectRefs at the Layer/View level.

I really don't like the idea of #1 above and moving further from the built-in object ref system. I am investigating the second idea.