Fix segment metadata query inconsistency bug with HLLSketch columns

[jtuglu1]

Fixes #14315.

Description

As outlined in #14315, segment metadata queries issued against complex columns served by realtime data nodes (IncrementalIndex) can potentially clash with type names of the same column (in QueryableIndex) served by historical nodes. I thought the best way to solve this was ensuring that the column type used is consistent across both data serving nodes (e.g. realtime and historical), rather than attempting to do some case-by-case coverage. Keeping as draft until I can confirm this doesn't break any other codepaths.

Release note

Fix segment metadata query type inconsistency bug when querying between realtime and historical sketch columns.

---

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.

[abhishekrb19]

Thanks for the fix, looks good to me. I had a question about whether this also applies more generally in cases where we have different aggregators for the build vs output types (not just HLLSketch columns).

[abhishekrb19]

Thanks! Could you also add a note to the release notes mentioning that this fix applies to other sketch aggregators as well?