[CAR-405] Fixing Async + Websocket Issues

[chongzluong]

Ticket: https://linear.app/cartesia/issue/CAR-405/[python-client]-async-websocket-issues

Seems like we might be running into some issues related to interruptions or the like? I think the suggesiton was that when an async client makes subsequent requests to the server, we sometimes get issues with long sequences suggesting that there might be an issue with how we're handling the web socket.

However in practice I appear to be unable to reproduce this behavior.

A few changes here:

• Test utility to turn PCM to WAV files
• A test script for testing the websockets behavior in async and sync clients
• Made voice a required param in the TTS Client
• (This PR might turn into primarily this) Fixed the docstrings for the TTS Client generation

[linear[bot]]

CAR-405 [Python Client] Async + Websocket Issues

Per conversation with kavan.doctor: Might be a small bug in how web socket handles async. What we think is happening: * When a client makes a 2nd request to the server, async client makes another generation request * Websocket is not being flushed * Testing might be hard * Launch a long sequence of text - currently we only accept up to 400 characters * Immediately launch another one * Perhaps in repo test

[chongzluong]

The docstring and default fixes seem like good changes. Why don't we get those in anyway and split off the bug investigation? Even if both were complete now, small bite-sized PRs are good

Haha fair enough I'll separate that out

[chongzluong]

Given that we're unable to reproduce, closing this out for now