Support KQL in TSVB Filter aggregation

[TinaHeiligers]

In the Visual Builder, the time series visualization only accepts Lucene syntax in the

1. Data -> Options -> Filter,
2. Data -> Metrics -> Group by -> Query string (when grouping by a single filter or many filters),
3. Panel Options -> Data Panel -> Filter
4. Annotations -> Data Source -> Query string.

Using KQL with the autocomplete it offers will make it easier to create a query without the need to remember the exact field name and it assists with operators and values.

In each of the TSVB situations given above, we need a query bar without a submit button. Ideally, it should be a QueryBarInput component that is just the text input, the query language switcher and autocomplete. One is being created for KQL in the filters aggregation (#29790)

References #29790, #30177

[elasticmachine]

Pinging @elastic/kibana-app

[TinaHeiligers]

The following points were raised after implementation discussions:

1. The modified version of the QueryBar will need to accept lucene syntax.
2. The implementation has to deal with the fact that the saved visualization queries are in lucene, and have the ability to detect and differenciate between lucene and KQL syntax in saved visualizations. A saved object migration is necessary for that.
3. The query string is currently passed as is to the server. The server then parses it into an ES query for the request.
   Everything is more or less in the file src/legacy/core_plugins/metrics/server/lib/vis_data/request_processors/series/query.js
   where we have the main filters, one on each series and one on the panel and they are applied to the ES query as:

if (panel.filter) {
      doc.query.bool.must.push({
        query_string: {
          query: panel.filter,
          analyze_wildcard: true,
        },
      });
    }

    if (series.filter) {
      doc.query.bool.must.push({
        query_string: {
          query: series.filter,
          analyze_wildcard: true,
        },
      });
    }

4. The filter strings will need to be parsed according to the syntax they are composed in, checked for errors by the QueryBar and then sent as plain query strings to the server.
5. On the server side, the string needs to be detected and included as part of the other filters used to build the main query in:

doc.query = buildEsQuery(indexPattern, queries, filters, esQueryConfig);

[TinaHeiligers]

Steady progress is being made with KQL supported in TSVB using the QueryBar component.

Remaining items:

• Implement the QueryBarInput Extract QueryBarInput component from QueryBar
• update tests
• general code enhancements

[TinaHeiligers]

Closed with merged PR #36784