raise the datastream WebSocket message size limit (SCH-7098)

[schematic-orbit]

websockets.connect() never passed max_size, so the datastream client kept the library's 1 MiB default. Syrto's rulesengine.Flags frame is 1,125,653 bytes, so the library closes the connection with a 1009 and the client reconnects straight into the same frame — ~1,000 reconnects an hour since they crossed 1 MiB on 2026-09-04. Flag checks stay correct because check_flag_with_entitlement falls back to REST, but the datastream never delivers anything. Python is the only SDK affected: schematic-node inherits ws's 100 MiB maxPayload and the Go replicator never calls SetReadLimit.

Pass an explicit 100 MiB max_size to match Node, exposed as max_message_size on ClientOptions, DataStreamClientOptions and DataStreamConfig.

Second change in the same file: _reconnect_attempts was cleared on every successful handshake, so a failure that always lands after connecting never escalated past the ~1s backoff floor. It now clears once the connection delivers a message or stays up 30 seconds. Consequence worth a look in review — a permanently poisoned connection now exhausts max_reconnect_attempts and fires on_error instead of churning forever.

Not addressed here: 740 rules already yields a 1.1 MB frame and Airia prod is ~10x that, so a client cap is not a durable answer. EnableCompression on the datastream upgrader in schematic-api would cut this payload ~10x — worth its own ticket.