[Console Monaco migration] Fixes

[yuliacech]

Summary

Fixes #184927
Fixes #184584
Fixes #184447

This PR fixes various issues in the migrated Console:

• The url params with whitespaces are now parsed correctly and the whole values is sent in the request ([Console Monaco migration] Add support for url param values with whitespaces #184927)
• The autocomplete for fields only shows the fields of the current index ([Console] Fields autocomplete suggestions are shown for all indices #184584)
• The popup with autocomplete suggestion is not covered by the resizer bar ([Console Monaco migration] Fix autocomplete popup css #184447)

How to test

1. Send a request with a url param that contains a whitespace, for example GET _search?q="test test". The request should be executed correctly.
2. Create an index with only 1 field

PUT field_test/_doc/1
{
  "test": 1
}

Try a search query with the fields autocomplete and check that only 1 field is suggested

GET field_test/_search
{
  "query": {
    "match": {
      "

3. Check that the popup with autocomplete suggestions is not covered by the resizer bar

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
• Flaky Test Runner was used on any tests changed
• 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

[yuliacech]

/ci

[elasticmachine]

Pinging @elastic/kibana-management (Team:Kibana Management)

[yuliacech]

changes in this test files is the reverse of changes in this PR #162917

[yuliacech]

changes in this test files is the reverse of changes in this PR #162917

[ElenaStoeva]

Thanks for working on these fixes @yuliacech! Tested locally and the behavior in the described cases is correct. Code changes also LGTM.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 8cd1669

Failed CI Steps

• FTR Configs #78

Test Failures

• [job] [logs] FTR Configs #78 / discover/esql discover esql view test should perform test query correctly

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
console	456.8KB	457.0KB	+165.0B

Page load bundle

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

id	before	after	diff
console	32.9KB	33.0KB	+124.0B

History

• 💛 Build #217155 was flaky 0559e32
• 💔 Build #217099 failed a24550c
• 💔 Build #216767 failed 316e9a4

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