fix: forward query routing options

[jstirnaman]

What changed

Query routing options (params, timeoutMs) now propagate to the product-type-specific query executors instead of being silently dropped.

• executeCloudDedicatedQuery and executeCloudServerlessQuery accept options and pass named params to the Flight client's queryPoints.
• executeClusteredQuery accepts options and forwards params/timeout to the HTTP request.
• Added flightParams() to validate Flight-unsupported inputs: rejects timeoutMs (Flight has no per-query timeout), rejects array-style params (Flight requires named params), and rejects non-primitive param values.
• InfluxQL query path (executeClusteredQuery callsite) also now forwards options.

Why

The public query methods accepted options but the private per-product executors ignored it, so callers passing query params or a timeout got no error and no effect — the option was silently discarded.

Impact

• Core/Enterprise callers: unaffected (already forwarded options).
• Cloud Dedicated / Cloud Serverless (Flight): params now actually apply to queries; timeoutMs and array params now throw instead of being ignored.
• Clustered: params/timeoutMs now forwarded to the HTTP query request.

Verification

• npm run build — clean
• npm test — 91 passed, 28 skipped
• Added tests/query-routing.test.ts covering options forwarding and the new Flight validation errors