[XTA-15079] Add SPOG ?o= routing support and fix final-flush auth on close

[samikshya-db]

Summary

Ports the SPOG (Single Panel of Glass) routing fix from
databricks/databricks-jdbc#1316
to the Node.js driver, and fixes a related close-ordering bug uncovered
while validating the port against a real SPOG host.

Change 1: SPOG header injection

SPOG replaces workspace-specific hostnames with account-level vanity URLs.
When httpPath carries ?o=<workspaceId>, endpoints that don't include
the workspace in their URL path need the workspace conveyed via the
x-databricks-org-id header instead.

• Parse ?o=<digits> out of httpPath in DBSQLClient.connect() and
  stash the org-id as x-databricks-org-id on a new
  ClientConfig.customHeaders field. A user-supplied customHeaders
  entry (case-insensitively keyed) takes precedence.
• DatabricksTelemetryExporter spreads config.customHeaders into the
  outgoing POST headers; auth headers still win on collision.
• FeatureFlagCache does the same for the feature-flag GET.
• ConnectionOptions.customHeaders exposed so callers can also inject
  their own out-of-band headers.

OAuth / OIDC token requests use openid-client's private HTTP transport
and never see customHeaders, matching JDBC's exemption.

Not needed vs JDBC: this driver passes options.path through
unmodified (no split-on-= parser), uses Thrift only (no SEA JSON body
warehouse-ID extraction), and exposes no Volume API surface.

Change 2: Close-ordering fix

While verifying Change 1 against a real SPOG warehouse, the final
client.close() flush emitted:

[warn] Telemetry: Authorization header missing — metrics will be dropped
[debug] Telemetry export auth failure: Telemetry export: missing Authorization header

Root cause: TelemetryClientProvider.releaseClient called
unregisterContext before client.close(). On the last refcount, that
emptied the FIFO of (context, authProvider) pairs before the final
flush, so the exporter's getAuthProvider() walk returned undefined and
the batch was dropped.

Fix: skip the unregister on the last release so the FIFO snapshot
survives through close()'s final flush. Multi-refcount path is
unchanged. No leak — the TelemetryClient is unreachable as soon as
releaseClient returns, and the retained (context, authProvider)
pair dies with it.

Live verification

Ran against dogfood-spog.staging.azuredatabricks.net warehouse
ad6f9b54e6593746?o=7064161269814046:

customHeaders={"x-databricks-org-id":"7064161269814046"}     ← SPOG header injected
Feature flag enableTelemetryForNodeJs: true                  ← header propagated via SPOG
Result: [{"v":1}]                                            ← SELECT 1 worked
Successfully exported 3 telemetry metrics                    ← final flush no longer drops

Test plan

Unit tests added (all passing locally):

• buildCustomHeaders parses ?o= into x-databricks-org-id
• No header when ?o= is absent and no user-supplied customHeaders
• User-supplied customHeaders is preserved alongside parsed org-id
• User-supplied x-databricks-org-id (any case) wins over ?o=
• Non-numeric o=<value> does not inject a header
• End-to-end DBSQLClient.connect() populates
  config.customHeaders['x-databricks-org-id'] from the path
• DatabricksTelemetryExporter attaches config.customHeaders to
  the POST headers
• Auth headers still override customHeaders on key collision
• No header is attached when config.customHeaders is empty
• FeatureFlagCache.fetchFeatureFlag attaches customHeaders to
  the GET headers
• releaseClient keeps the context registered through close() on
  last refcount
• releaseClient drops the context immediately when other
  refcounts remain

This pull request and its description were written by Isaac.

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[msrathore-db]

Please verify all purpose cluster url is working and also M2M is working

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[samikshya-db]

Thanks for the review, @msrathore-db !
Addressed the comments.

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).