feat(node): add paramters to forward OTEL Headers to Clickhouse

[DylanRJohnston]

Summary

Addresses #394, Clickhouse supports reading the OTEL HTTP headers from the connection

Checklist

• Unit tests covering the common scenarios were added
• A human-readable description of the changes was provided to include in CHANGELOG

[CLAassistant]

All committers have signed the CLA.

[slvrtrn]

Thanks for the contribution.
I think it makes more sense to just allow overriding headers for a particular request in all methods. It also looks like that's what initially was proposed in the code snippet in the issue.
@mshustov WDYT?

[DylanRJohnston]

@slvrtrn that makes sense, but what about the existing auth configuration parameters that get turned into headers? Should custom headers override them, or visa versa?

[DylanRJohnston]

Also I had a look at the failing integration tests it seems that the CI environment is misconfigured?

[mshustov]

I think it makes more sense to just allow overriding headers for a particular request in all methods. It also looks like that's what initially was proposed in the code snippet in the issue.

👍

what about the existing auth configuration parameters that get turned into headers? Should custom headers override them, or visa versa?

I'd vote for allowing users to override any headers (with a debug log record emitted that an override has happened) - it gives more power and flexibility to the end user. For example, one can implement multi-tenant runtime and mange users on the app level