Include better output in profiling & toString for automaton based queries

[benwtrent]

We have various automaton based queries that build particular automatons based on their usage. However, the input text isn't part of the toString output, nor the usage of the current query (wildcard, prefix,etc.).

This commit adds a couple of simple queries to wrap some of our logic to make profiling and other output more readable.

Here is an example without this change:

#(-(winlog.event_data.TargetUserName:AutomatonQuery {
org.apache.lucene.util.automaton.Automaton@2d13c057} winlog.event_data.TargetUserName:AutomatonQuery {
org.apache.lucene.util.automaton.Automaton@28daf002} winlog.event_data.TargetUserName:AutomatonQuery {
org.apache.lucene.util.automaton.Automaton@43c3d7f8} winlog.event_data.TargetUserName:AutomatonQuery {
org.apache.lucene.util.automaton.Automaton@2f52905} winlog.event_data.TargetUserName:AutomatonQuery {
org.apache.lucene.util.automaton.Automaton@31d75074})

We have 5 case-insensitive automatons, but we don't know which is which in the profiling output. All we know is the originating field.

I don't think we can update AutomatonQuery directly as sometimes the automaton created mutates the term (prefix for example) and we lose that we are searching for a prefix.

[elasticsearchmachine]

Pinging @elastic/es-search (Team:Search)

[elasticsearchmachine]

Hi @benwtrent, I've created a changelog YAML for you.

[carlosdelest]

LGTM 👍

[benwtrent]

@elasticmachine update branch

[javanna]

shouldn't we have tests added to verify the change in behavior?