[Data][Filters] Move more filter utils to package and cleanup API

[lizozom]

Summary

Partially addresses #104140

Release Note

The following filter related utilities were marked as deprecated when imported from the data plugin.
Please import them from @kbn/es-query.

On the client side:

• esFilters is now deprecated
  • FilterLabel, FilterItem, getDisplayValueFromFilter, generateFilters, extractTimeRange can be imported from data\public (not using esFilters).
  • The following utility functions are available to be imported from @kbn/es-query
    • COMPARE_ALL_OPTIONS
    • compareFilters
    • enableFilter
    • pinFilter
    • toggleFilterDisabled
    • dedupFilters
    • onlyDisabledFiltersChanged
    • uniqFilters
  • The following functions are marked from deprecation and won't be part of the 8.0 public API
    • convertRangeFilterToTimeRangeString
    • extractTimeFilter
    • changeTimeFilter
    • mapAndFlattenFilters

On the server side:

• esFilters is now deprecated
  • All utility functions are available to be imported from @kbn/es-query

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[lizozom]

@elasticmachine merge upstream

[lukasolson]

Code changes LGTM, added a couple minor notes below

[lukasolson]

Any reason not to deprecate this now?

[lizozom]

I think this would be considered a breaking change, no?

[lukasolson]

Nah, deprecating something isn't a breaking change

[lizozom]

I changed the text to "removed"

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e70cefc
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
data	592	596	+4
infra	939	947	+8
maps	797	805	+8
securitySolution	2322	2330	+8
total			+28

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
data	3162	3189	+27

Any counts in public APIs

Total count of every any typed public API. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats any for more detailed information.

id	before	after	diff
data	98	99	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
infra	1.7MB	1.7MB	+22.0B
maps	3.2MB	3.2MB	+23.0B
securitySolution	6.4MB	6.4MB	+26.0B
total			+71.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
data	837.7KB	840.1KB	+2.4KB

Unknown metric groups

API count

id	before	after	diff
data	3716	3738	+22

References to deprecated APIs

id	before	after	diff
canvas	51	53	+2
dashboard	128	145	+17
dashboardEnhanced	10	13	+3
discover	102	129	+27
discoverEnhanced	19	21	+2
lens	160	166	+6
maps	592	608	+16
observability	34	42	+8
securitySolution	881	909	+28
visualizations	32	34	+2
total			+111

History

• 💚 Build #140720 succeeded 05d29a7
• 💚 Build #140447 succeeded 838b131
• 💔 Build #140432 failed 670249f

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @lizozom

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.