Add talk message stream

[sebvanleuven]

send_talk_stream was preliminary implemented very basic and required the dev to manage the correlation_id, while it did not provide any hooks for the interrupt.
The new approach now clears talk_stream buffers (by deleting the object) and manages the correlation_id, while still allowing devs to use their own correlation_id for debugging purposes.

---

Summary by cubic

Adds a TalkMessageStream for TTS that manages a stable correlation_id per stream, tracks stream state, and wires interruption events to make streaming simpler and more reliable. Updates the client API, signaling, and docs to use create_talk_stream, with send_talk_stream for one-off messages.

• New Features

  • Added TalkMessageStream with send(content, end_of_speech) and end(); correlation_id set at stream creation (optional override). Exports TalkMessageStream and TalkMessageStreamState.
  • New session.create_talk_stream(...) for grouped chunks; session.send_talk_stream(content) for single messages.
  • StreamingClient adds on_talk_stream_interrupted callback; client emits AnamEvent.TALK_STREAM_INTERRUPTED.
  • Signalling send_talk_stream_input now requires correlation_id (managed by the stream).
  • README/examples updated; version bumped to 0.3.0.
  • Unit tests added for TalkMessageStream (state transitions, interruptions, end behavior).

• Migration

  • Replace session.send_talk_stream(content, start_of_speech, end_of_speech, correlation_id) with session.create_talk_stream().send(...).
  • For single messages, use session.send_talk_stream(content).
  • If using low-level signaling, pass correlation_id explicitly.

^{Written for commit 9b845c6. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 9 files