Add MV_FILTER_REGEX and MV_FILTER_PREFIX SQL functions

[jtuglu1]

Fixes #12911.

Description

• Adds MV_FILTER_REGEX and MV_FILTER_PREFIX SQL functions.
• Creates 2 new VirtualColumn implementations: RegexFilteredVirtualColumn and PrefixFilteredVirtualColumn.
• Updates RegexpLikeExprMacro to support dynamic pattern literals (similar to how RegexpReplaceExprMacro does).

Examples

For following datasource:

-- returns rows: null, ["apple", "apple2", "apricot"], null, null
SELECT MV_FILTER_PREFIX("items", 'a')
from "mvs"

-- returns rows: null, "banana", "blueberry", null
SELECT MV_FILTER_PREFIX("items", 'b')
from "mvs"

-- returns rows: null, ["apple", "apple2", "apricot"], null, null
SELECT MV_FILTER_REGEX("items", 'a.*')
from "mvs"

-- returns rows: null, "banana", null, null
SELECT MV_FILTER_REGEX("items", '.*anana')
from "mvs"

-- returns rows: null, ["apple", "apple2"], null, null
SELECT MV_FILTER_PREFIX("items", 'apple')
from "mvs"

-- returns rows: null, ["apple", "apple2", "apricot", "banana"], ["blueberry", "chocolate"], "grape"
SELECT MV_FILTER_PREFIX("items", '')
from "mvs"

-- returns rows: null, ["apple", "apple2", "apricot", "banana"], ["blueberry", "chocolate"], "grape"
SELECT MV_FILTER_REGEX("items", '.*')
from "mvs"

-- returns rows: null, null, null, null
SELECT MV_FILTER_PREFIX("items", 'test')
from "mvs"

-- returns rows: null, null, null, null
SELECT MV_FILTER_REGEX("items", '')
from "mvs"

Release note

Add MV_FILTER_REGEX and MV_FILTER_PREFIX SQL functions

---

Key changed/added classes in this PR

• MyFoo
• OurBar
• TheirBaz

---

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.

[jtuglu1]

@clintropolis I may still cleanup the RegexpLikeMacro logic a bit to share more validations/checks, but LMK what you think otherwise.

[clintropolis]

overall lgtm, nice to have these other DimensionSpec migrated over to virtual columns. Someday I would like do deprecate DimensionSpec other than DefaultDimensionSpec and do all of the others as virtual columns, so this aligns well with that.

The virtual columns are missing an implementation of getIndexSupplier, so using them for filtering directly is probably sub-optimal, however that is also probably ok because i think the primary use of these functions are so you can tidy up an MVD and not see seemingly unrelated values when using a filter on the column itself due to how filters behave on mvds (if any value in the row matches the whole row matches, and when using grouping the implicit unnest results in the other non-matching row values appearing in results). So like as long as people are just using the MV_ functions in the select clause and just using the column itself and the regular filter in the where clause it shouldn't be a big deal.