Re-export ResponseHeaders from client-node and client-web

[Copilot]

Summary

Prepping @clickhouse/client-common for deprecation. Audited the types hyperdxio/hyperdx imports from it (BaseResultSet, ClickHouseSettings, DataFormat, ResponseHeaders, ResponseJSON, Row, ClickHouseClient) against the re-export allowlists in @clickhouse/client and @clickhouse/client-web. All but ResponseHeaders were already exposed.

• Added type ResponseHeaders to the common re-export blocks in packages/client-node/src/index.ts and packages/client-web/src/index.ts.

Checklist

• A human-readable description of the changes was provided to include in CHANGELOG

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Copilot]

Pull request overview

This PR exposes ResponseHeaders as part of the public type surface of @clickhouse/client (node) and @clickhouse/client-web, reducing the need for downstream users to import it from @clickhouse/client-common ahead of that package’s planned deprecation.

Changes:

• Re-exported type ResponseHeaders from @clickhouse/client-common in the node client entrypoint.
• Re-exported type ResponseHeaders from @clickhouse/client-common in the web client entrypoint.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/client-node/src/index.ts	Adds ResponseHeaders to the explicit re-export allowlist from @clickhouse/client-common.
packages/client-web/src/index.ts	Adds ResponseHeaders to the explicit re-export allowlist from @clickhouse/client-common.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!