Wrong cursor position when entering non-latin (Cyrillic) chars in filter string

## Expected Behavior

When entering text into a Search Filter textbox, regardless of the language, cursor always reflects actual insertion point

## Current Behavior

When entering text with Cyrillic characters into a Search Filter textbox, the more text is entered, the more is the difference between the insertion point and visible cursor position. I.e. the cursor is several characters "behind" of the position where the characters are actually inserted at.

## Possible Solution

Revert to Chrome <=109.0.5414.74, where the issue is not reproducible.

## Steps to Reproduce (for bugs)

1. Go to Graylog "Search" tab.
2. Enter non-latin characters (in my case Cyrillic)
3. Observe how the blinking cursor position "lags behind" pixel by pixel
4. After approximately 8 characters the lag is equal to one char, and growing

## Context

It's very hard to edit complex queries when one does not understand where your actual cursor is. With autocomplete kicking in, the text box becomes barely usable.

## Your Environment

* Graylog Version: 5.0.6 on Linux 5.19.0-38-generic
* Java Version:
* Elasticsearch Version:
* MongoDB Version:
* Operating System: Windows 11, Ubuntu 22
* Browser version: Chrome 112.0.5615.138, Edge 112.0.1722.58, Firefox 112.0.1