Pass query params and timeout through every supported product route

## Problem

`query_sql` and `query_influxql` accept `params` and `timeoutMs`, but `QueryService.executeQuery` drops those options on Cloud Dedicated, Clustered, and Cloud Serverless routes. Those branches call their downstream query methods with only the query and database.

Parameterized queries can consequently fail or run without their bindings on supported product types, despite the public MCP contract.

## Expected behavior

Forward the complete query options contract, including `params` and `timeoutMs`, through Cloud Dedicated, Clustered, and Cloud Serverless routes as well as Core/Enterprise.

## Acceptance criteria

- Routing tests assert that each supported product type receives `params` and `timeoutMs`.
- `query_sql` and `query_influxql` preserve options end-to-end where each backend API supports them.
- Unsupported backend options are handled explicitly rather than silently discarded.

## Release assessment

Fixable for 1.4.0 and recommended before release because it restores the documented API contract. It is not a read-only safety bypass.

Start at QueryService.executeQuery and trace the Cloud Dedicated, Clustered, Cloud Serverless, Core, and Enterprise branches into query_sql and query_influxql. Run or extend the routing tests mentioned in the issue to verify params and timeoutMs are preserved for every supported product type. Done means supported options reach each backend, while unsupported options are handled explicitly.

Written by the indexing model from the issue text.