Automatically set `query_id`

### Use case
ClickHouse supports the `replace_running_query` feature: https://clickhouse.com/docs/operations/settings/settings#replace_running_query

`query_id` can be set manually via `with_option()`, but we should be setting this automatically.

### Describe the solution you'd like

* `Query::get_query_id()`
* If `query_id` is not previously set, generate and store a query ID to return it? E.g. using `OnceLock`?
* `Query::with_query_id()`
* Like other explicit setters, easier to discover and use than `with_option()`.

Questions:
- [ ] Should `Insert` and `Inserter` gain this as well?

### Describe the alternatives you've considered

### Additional context
1.0 wishlist: feature parity

Start by locating Query's existing with_option implementation and any current query_id handling. Compare the proposed get_query_id and with_query_id behavior with the existing explicit setters, then determine whether Insert and Inserter should support the same API. Done means an unset query receives a stored generated ID, explicit IDs remain usable, and the chosen scope is covered by tests.

Written by the indexing model from the issue text.