Websocket API: Light transaction updates & `NoSuccessNotify`

[Centril]

Description of Changes

Does two things:

1. Adds TransactionUpdateLight that consists only of the request_id and the DatabaseUpdate<F>. This is emitted when the query param &light=true is set (unless the update is sent to the caller in which case a full update is sent).
2. Adds flags: enum CallReducerFlags { FullUpdate, NoSuccessNotify } to ClientMessage. When NoSuccessNotify is set, the host will not send back an empty update to the caller on success without the caller having subscribed to any affected queries. This is exposed in the SDK via ctx.set_reducer_flags.my_reducer(CallReducerFlags::NoSuccessNotify). When the default FullUpdate is used, full updates are sent, whether the caller was subscribed to the relevant queries or not.

TODO:

• [x] Host implementation of the above.
• [x] Rust SDK implement of the above.
• [x] C# SDK implementation of the above, https://github.com/clockworklabs/com.clockworklabs.spacetimedbsdk/pull/170
• [x] TS SDK implementation of the above, https://github.com/clockworklabs/spacetimedb-typescript-sdk/pull/110

API and ABI breaking changes

This breaks the websocket API/protocol.

[bfops]

Looks like the tests are failing?

[bfops]

@Centril I'm happy to review the CLI changes - Do you have recommendations on how to test this? Should I just regenerate bindings for an example client for each language?