subscription event handling

[snvfk1n]

right now, we push the whole document state to subscribers when changes occur. this, however, can lead to bottlenecks especially when considering the WS bridge and gateway in the gateway process.

• make change requests transmit their responses before sending out subscriber pushes
• try out hash-based diffing for watch handlers and sparsely transmit changes to subscribers
• debounce watch calls?