[hsdfat]

Summary

Fixes #477

When insert validation fetches a table schema, its internal DESCRIBE TABLE inherits the client's query_id. Reusing that ID for the subsequent INSERT makes the query log ambiguous and can trigger QUERY_WITH_SAME_ID_IS_ALREADY_RUNNING.

The schema lookup now uses {query_id}-describe, preserving its link to the original INSERT while assigning the two requests distinct IDs. The INSERT retains the caller's ID. session_id and all other settings are preserved, and absent or empty IDs retain server-generated ID behavior. This also covers Inserter.

Unit tests verify derived IDs, preserved client/session settings, and absent/empty IDs. Integration tests inspect system.query_log and assert that the linked ID belongs to Describe and the original ID belongs to Insert, for both direct inserts and Inserter.

Validation after rebasing onto current main:

• cargo test --lib --all-features: 109 passed.
• cargo test --test it --all-features insert -- --test-threads=2: 40 passed against ClickHouse 26.9.3.38, including temporary-table/session tests and both regressions.
• Both new query-log regressions also pass against ClickHouse 25.8.33.6.
• cargo clippy --all-targets --all-features -- -D warnings
• cargo clippy --all-targets --no-default-features -- -D warnings
• cargo fmt --all -- --check

Checklist

• Unit and integration tests covering the common scenarios were added
• A human-readable description of the changes was provided so that we can include it in CHANGELOG later

[CLAassistant]

All committers have signed the CLA.

[abonander]

@hsdfat I cannot merge your PRs unless you sign the CLA as shown above.

[hsdfat]

The CLA assistant now reports all committers signed on both PRs: #481 and #478. Those status updates came after your comment. Could you recheck whether anything else is needed on my side?