[Dashboard] [Controls] Add "Exists" functionality to options list

[Heenawter]

Closes #140700
Closes #139932

@elastic/kibana-docs Refer to #143762 (comment)
@elastic/kibana-design Refer to discussion starting at #143762 (comment)

Summary

This PR adds the ability for the options list control to be used as an exists filter for a given field.

Screen.Recording.2022-10-25.at.2.58.41.PM.mov

The exists option list entry will show up at all times, even during search, unless one of the following conditions is met:

1. The exists option is not selected and "Show only selected" is selected in the dropdown
2. The "Allow exists query" toggle is set to false in the create/edit control flyout
3. The options list has no suggestions due to chaining, search string returning no results, etc.

Screen.Recording.2022-10-26.at.9.49.09.AM.mov

As part of this, I performed a refactor of the OptionsListPopover component because, with the addition of both the exclude and exists functionality, the logic was starting to get extremely difficult to follow. This included making it so that the search bar auto focuses when the popover is open.

How to Test

Testing general exists / does not exist queries:

1. Download the following test data I generated: testExistsData.csv
2. Upload this data to Kibana
3. This data has 100 rows and two columns - one, that always has a value (always exists) and two, which has a value 57 times (sometimes exists). Verify that, when creating a control for these fields, you get the expected results for the exists and does not exist queries.

Warning
After discussion with @andreadelrio, we decided that the validation should not apply to the exists selection because you can get unexpected results - for example, if a field always exists, a "Does not exist" selection would automatically jump to "Ignored selections" when validation was on.

In this case, a "no data" state actually makes it clearer to the user that the field simply always exists, whereas the selection automatically being ignored causes confusion on why their selection does not apply. So, since the exists query is special in this way, it should never be ignored - i.e.exists or does not exist selections should always apply regardless of if the selection results in a no data state.

Therefore, the following discussion is outdated / no longer relevant:

#### Testing validation of `exists` and `does not exist` queries:
1.  Download the smaller test data if you want, since it's easier to test the validation with this: [testSmallExistsData.csv](https://github.com/elastic/kibana/files/9922840/testSmallExistsData.csv). Note that this dataset is simply the first 10 rows of the original dataset, so feel free to modify that dataset if you'd prefer.
2. Add a control for `always exists` followed by a control for `sometimes exists`
3. One way to get an invalid `does not exist`  selection...
    1.  In the `always exists` options list, exclude the selections and select `Does not exist (!)` 
    2. This selection should automatically be ignored<br>
     ![Nov-02-2022 14-54-09](https://user-images.githubusercontent.com/8698078/199600579-09d8f77d-ad3c-4a1e-a10c-a2714273f2f9.gif)

4. Another way to get an invalid `does not exist`  selection...
    1. In the `sometimes exists` options list, exclude the selections and select `Does not exist (!)` 
    4. In the `always exists` options list, select `"Katherine Marshall"` and `"Suzanne Howard"`
    5. Notice that the `Does not exist (!)` selection in the `sometimes exists` options list is invalid<br>
     ![image](https://user-images.githubusercontent.com/8698078/199601370-fb09606e-15df-4de5-a722-9e114f938698.png)

7. To get an invalid `exists` selection...
    1. In the `sometimes exists` options list, include the selections and select `Exists (*)` 
    2. Keep the selections from step 4(ii) above, but toggle `exclude` to `true`
    4. Notice that the `Exists (*)` selection in the `sometimes exists` options list is invalid<br>
      ![image](https://user-images.githubusercontent.com/8698078/199601533-79b74a85-32b0-4c24-902d-17a584c979df.png)

Flaky Test Runner

• control_group_chaining.ts
  

• options_list.ts
  

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
• 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)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[Heenawter]

Tried to add this space using CSS :after, but then this messes with the screen reader because the title of the button becomes "DOES NOTExist"- so, need to add the space explicitly here instead.

[andreadelrio]

Design LGTM, great job! Exciting to see controls getting closer to filter pills.

[ThomThomson]

Tested this locally and all of the test cases I could think of worked properly, including any weird settings on the chain, and turning on and off the exists capabilities in various selection states. ✅

Code wise, the new organization of the Options List Popover into 3 components looks great! It's much more organized, and is a good foundation for adding even more features & complexity to the Options List. ✅

Also great looking unit test and functional test coverage! ✅

[ThomThomson]

It's too bad there isn't a helper for this function. Do other functional tests that you've seen use the console to add docs?

[Heenawter]

I actually wasn't able to find any tests that add new documents except those that are literally testing the console 😅 So I just came up with my own way of doing it

[ThomThomson]

There's a first time for everything I guess! If we find ourselves having to do this more and more, we should create our own helper then maybe.

[ThomThomson]

Agreed, no reason to also test scripted fields here as well.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: a87f33d

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
controls	152	156	+4

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
controls	224	228	+4

Async chunks

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

id	before	after	diff
controls	471.6KB	473.6KB	+2.0KB

Page load bundle

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

id	before	after	diff
controls	20.6KB	21.9KB	+1.3KB

Unknown metric groups

API count

id	before	after	diff
controls	233	237	+4

ESLint disabled in files

id	before	after	diff
osquery	1	2	+1

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	19	21	+2
fleet	58	64	+6
osquery	106	111	+5
securitySolution	440	446	+6
total			+19

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
fleet	66	72	+6
osquery	107	113	+6
securitySolution	517	523	+6
total			+20

History

• 💚 Build #85307 succeeded 64c11c9
• 💔 Build #85271 failed 0318b0a
• 💔 Build #85268 failed 8f255b46f9779d648341c64f19094271bc24d2a9
• 💔 Build #85246 failed 20a1dd2
• 💔 Build #85235 failed b1bbfc8
• 💔 Build #85183 failed 8af6c57

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

cc @Heenawter