feat: make retry-policy knobs configurable via connect() (both backends)

[msrathore-db]

Problem

The retry-policy knobs — retryMaxAttempts, retriesTimeout, retryDelayMin, retryDelayMax — lived only in the internal ClientConfig (defaults 5 / 15min / 1s / 60s). The Thrift HttpRetryPolicy reads them, and #420 forwarded them to the kernel on the SEA path via buildKernelRetryOptions(getConfig()). But:

• they were not declared on ConnectionOptions, and
• connect() never copied them from user options into ClientConfig (it copies metricView / precision / telemetry / userAgentEntry / customHeaders, but not these).

So a caller passing retryMaxAttempts: 2 had no effect on either backend — the hardcoded defaults always applied. (#420 made SEA consume the same ClientConfig knobs as Thrift — parity of consumption — but did not add a way to set them.)

Confirmed empirically before the fix (persistent-429 fault on SEA):

retryMaxAttempts=2 → 5 attempts   (default, override ignored)
retryMaxAttempts=0 → 5 attempts   (override ignored)

Change

• Declare the four knobs on ConnectionOptions (with JSDoc).
• Ingest them into ClientConfig in connect() (per-key narrowed copy, matching the existing metricView / precision / telemetry handling).

Because both backends already read ClientConfig — Thrift via HttpRetryPolicy.getConfig(), SEA via buildKernelRetryOptions(getConfig()) — this single change makes the knobs honored on Thrift and SEA simultaneously, at parity. No kernel change required.

Semantics

retryMaxAttempts=N caps at N total attempts (initial + retries combined); 0/1 both mean a single attempt, no retry. This is consistent across backends — Thrift's HttpRetryPolicy increments attempt then stops at attempt >= retryMaxAttempts, and the kernel converts the total to its after-initial retry count.

Verification

After the fix, end-to-end on SEA (persistent-429 fault, countSeaCalls('ExecuteStatement')):

retryMaxAttempts=2 → 2 attempts
retryMaxAttempts=0 → 1 attempt

(previously both produced the default 5). Plus unit tests asserting connect() ingests the options into ClientConfig and keeps defaults when omitted (2 passing). Source files lint clean.

This pull request and its description were written by Isaac.