Document production WebSocket reconnection, buffering and compression

[Lyptik]

Changes

Document recommended production integration practices in the SDK README:

• compression should be an explicit application choice and is recommended when a Zstd decompressor is available
• reconnect as a fresh Augmenta session and expect setup/state refresh
• clear stale application-side pending frames across reconnect/setup replacement
• ignore callbacks from superseded sockets
• never use an unbounded FIFO of complete tracking frames
• for render clients, use bounded latest-state-wins buffering per scene
• preserve transient events separately when frame conflation could otherwise drop them
• point developers to the Augmenta ThreeJS example as the browser reference implementation

The SDK remains transport/runtime neutral and does not impose a render buffering policy itself.