fix: fix query context precedence layer for datasource-level per-segment timeout

[jtuglu1]

Description

Currently, per-datasource, per-segment timeout can be not set if there's a hardcoded static default query context (druid.query.default.context.perSegmentTimeout). This ensures the evaluation precedence for the per-segment timeout is as follows (from highest to lowest):

1. Query-specified context values (passed in the query payload)
2. Dynamic configs (broker per-datasource per-segment timeout, broker dynamic config, etc.). Former beats the latter for this particular config.
3. Static defaults specified at process boot (druid.query.default.context.perSegmentTimeout)
4. Default values specified in the application code.

Also adds the perSegmentTimeout context key so it's easy to auto-complete in the UI.

Release note

Fix query context precedence layer for datasource-level per-segment timeout.

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[FrankChen021]

I have reviewed the code for correctness, edge cases, concurrency, and integration risks; no issues found.

Reviewed 4 of 4 changed files.

---

This is an automated review by Codex GPT-5.5

[maytasm]

nit: since it's not really clear from the variable names (userContextKeys vs userProvidedContextKeys), can you add a comment here on the difference between userContextKeys and userProvidedContextKeys

[jtuglu1]

Agreed. I've refactored since I didn't really want to leak this context override logic (per segment timeout, etc.) into the query handler code.

[FrankChen021]

I have reviewed the code for correctness, edge cases, concurrency, and integration risks; no issues found.

Reviewed 12 of 12 changed files.

---

This is an automated review by Codex GPT-5.5