Integrate painless autocomplete in runtime fields editor

[alisonelizabeth]

This PR integrates painless autocompletion in the runtime fields editor.

Continuation of #80577.

How to test

Verify autocomplete functionality is working in the runtime field editor. The runtime field editor is currently only integrated in the composable index template, legacy index template, and component template wizards.

For a list of available autocomplete functionality, check out the "Testing" section in #80577.

In order to test field autocompletion, you need to create at least one mapped field.

Known issues

I've received some feedback already around improvements that can be made to the autocomplete. I will handle these in a separate PR (#85055):

• Auto closing brackets
• Autocomplete support for emit() and params
• Filter out text field types from the field autocomplete suggestions; text field types are never in doc values.
• Autocomplete should not kick in for string and boolean values

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[alisonelizabeth]

@elasticmachine merge upstream

[alisonelizabeth]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 0c584d8

Metrics [docs]

Async chunks

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

id	before	after	diff
indexManagement	1.5MB	1.5MB	+32.0B

Distributable file count

id	before	after	diff
default	46921	47681	+760

Page load bundle

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

id	before	after	diff
runtimeFields	29.8KB	30.9KB	+1.1KB

History

• 💚 Build #92032 succeeded 5c64f52
• 💔 Build #91991 failed fd9f09b
• 💔 Build #91819 failed 8c043c1

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

[yuliacech]

Hi @alisonelizabeth , great job on adding autocomplete to runtime fields editor! I tested locally and all worked for me, changes in code LGTM too 👍