Move @kbn/es-query into data plugin

[lukeelmers]

In #42012 it was decided that we would move the @kbn/es-query package into the data plugin. This will help solve some problems of shared type interfaces (specifically Field and IndexPattern), but it also makes sense to have data be the home for this package.

Prepare @kbn/es-query for moving into data plugin:

• migrate to TS and tests to JEST for:
  • es-query [Move @kbn/es-query into data plugin - es-query folder #50182] @alexwizp;
  • filters [Move @kbn/es-query into data plugin - filters folder #49843] @alexwizp ;
  • kuery
    • Remove unused code - cleanup kuery folder [Move @kbn/es-query into data plugin - remove unused code #50903] @alexwizp;
    • Remove @kbn/es-query module and exclude it from the build process [Move @kbn/es-query into data plugin - kuery folder #51014] @alexwizp;
    • Replace all import links from @kbn/es-query -> 'src/plugins/data/{server|public} [Move @kbn/es-query into data plugin - kuery folder #51014] @alexwizp;
    • Migrate tests from Mocha -> Jest [Move @kbn/es-query into data plugin - kuery folder #51014] @alexwizp;
    • Migrate all files from ./es-query/kuery to typescript. - WIP
  • utils [Move @kbn/es-query into data plugin - es-query folder #50182] @alexwizp;

The utility functions and types will be exported from the data plugin grouped inside objects, to give them context:

export const filters = {
   // TYPES
   ExistsFilter,
   RangeFilter,
   ...
   // Utility functions
   buildExistsFitler,
   buildRangeFilter,
   ...
}

[elasticmachine]

Pinging @elastic/kibana-app-arch

[lizozom]

Please hold off on this task until we finish the data plugin RFC

[TinaHeiligers]

Please also reach out to me before starting this work. I need some of the methods in the package to be stateful and have access to saved objects so that we can use saved queries by reference rather than cloning them. This will allow us to keep saved queries used everywhere (including filters and filter aggregations) in sync.

[Bargs]

@alexwizp I heard you're starting to work on this. I wanted to let you know I have a couple of PRs that make significant changes and additions to the package. The larger PR is already fully implemented and tested and is only awaiting final review before merging, so you may want to hold off on the migration effort until that is in.

#47070
#49537