Blocked by elastic/elasticsearch#109093

In Kibana versions >= 8.10.x it was found a bug in the response of range queries when the mappings are of keyword type

Original ticket: #167139

The reason seems to be that version numbers will work correctly as keyword until the numbers have multiple digits in them.

Suggested solutions

1. Switching the field in question to “version”
2. Switching the field in question to “version” field type in newly created indices and fixing older indices using a runtime field (see this comment)
   This option seems a bit "hacky" and might also be slower.

Tasklist

Determine how updating this mapping would impact dashboards, visualizations, etc when agent.version may be mapped as two different types in query results.
This would be a breaking change and we should asses the possible impacts across the whole UI before proceeding with a fix.