[kql] Remove named args and unused geo functions

[lukasolson]

Summary

• Simplifies the KQL (kuery) grammar & types by removing the namedArg node type.
• Removes the unused geo_bounding_box and geo_polygon KQL functions.

The namedArg node type was used only by the range function to specify which operator was being used (<, <=, >, or >=). This was not necessary, as it can just be an additional argument to the function itself. Note that many of the tests that previously contained multiple inequality conditions were updated to only include one, as the grammar itself only supports this.

The geo_bounding_box and geo_polygon functions were vestiges of the very first version of the (experimental) Kibana query language (which was actually known as "Kuery"). These aren't supported in the current version of KQL (and haven't been for years).

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:AppServicesSv)

[Dosant]

code lgtm 👍
thanks for the deep dive explaining it

[Dosant]

Code owners were not trigger. I think we need to add that package to .CODEOWNERS

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: f068597
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
canvas	1071	1068	-3
dashboard	263	260	-3
data	509	506	-3
dataVisualizer	334	331	-3
fleet	553	550	-3
infra	920	917	-3
inputControlVis	104	101	-3
lens	732	729	-3
lists	297	294	-3
maps	807	804	-3
ml	1586	1583	-3
observability	341	338	-3
presentationUtil	284	281	-3
securitySolution	2818	2815	-3
timelines	287	284	-3
uptime	664	661	-3
visTypeTimelion	114	111	-3
visTypeVega	287	284	-3
total			-54

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
@kbn/es-query	162	160	-2

Async chunks

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

id	before	after	diff
canvas	1013.2KB	1010.4KB	-2.7KB
dashboard	275.1KB	272.4KB	-2.7KB
dataVisualizer	538.1KB	535.4KB	-2.7KB
fleet	644.6KB	641.9KB	-2.7KB
infra	991.3KB	988.6KB	-2.7KB
inputControlVis	80.5KB	77.8KB	-2.7KB
lens	1.1MB	1.1MB	-2.7KB
lists	143.3KB	140.6KB	-2.7KB
maps	2.6MB	2.6MB	-2.7KB
ml	3.5MB	3.5MB	-2.7KB
observability	362.1KB	362.1KB	-4.0B
presentationUtil	232.8KB	230.1KB	-2.7KB
securitySolution	4.6MB	4.6MB	-4.0B
timelines	229.7KB	227.0KB	-2.7KB
uptime	683.3KB	680.5KB	-2.7KB
visTypeTimelion	124.0KB	121.3KB	-2.7KB
visTypeVega	2.0MB	1.9MB	-2.7KB
total			-40.7KB

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
@kbn/es-query	12	11	-1

Page load bundle

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

id	before	after	diff
data	443.7KB	441.0KB	-2.7KB
observability	80.3KB	77.6KB	-2.7KB
securitySolution	244.9KB	242.1KB	-2.7KB
total			-8.1KB

Unknown metric groups

API count

id	before	after	diff
@kbn/es-query	214	212	-2

History

• 💛 Build #11824 was flaky 8229c21
• 💚 Build #11560 succeeded 8a9133e
• 💚 Build #9661 succeeded 1f361de
• 💚 Build #8466 succeeded eb8bd07
• 💔 Build #7744 failed e27cdee
• 💔 Build #7542 failed def21e9

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

cc @lukasolson

[kibanamachine]

💔 Backport failed

Status	Branch	Result
❌	9.0	The branch "9.0" is invalid or doesn't exist

To backport manually run:
node scripts/backport --pr 118973

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 118973 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 118973 or prevent reminders by adding the backport:skip label.