Collapse the history client API to one option and one method
Five methods was four too many. A frontend needs to say where runs go and read
them back, and `Client.connect(url, { history_bucket })` plus `read_history()`
covers both; the bucket can be repointed later through `client.options`.
Dropped `connect_history_bucket()` in particular: nothing has to be set up
before recording, because `save_record` already calls `ensure_bucket`, so the
first run recorded to a bucket creates it. `connect_bucket` and
`list_user_buckets` stay exported as plain functions for gradio's own settings
UI and the workflow canvas, and for a frontend that wants to confirm a bucket
is writable before relying on it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
