[Dashboard] [Controls] Add unmapped runtime field support to options list

[Heenawter]

Closes #144931

Summary

This PR adds options list support for runtime fields that are added to data views - note that runtime fields that are added as part of an index (i.e. they are part of the mapping) already worked as expected.

RuntimeFields.mov

How to Test

• Create some data view runtime fields of various types as described in the documentation. For example, in the sample Logs data view, you could create the following:
  • Keyword:

    emit(doc['referer'].value.splitOnToken('/')[2].replace(' ', ''))

  • Keyword with partial data (to test the exists options list functionality):

    if(doc['geo.dest'].value == 'US') {
        emit('Party in the USA')
    }

  • Boolean:

    emit(doc['geo.src'].value == doc['geo.dest'].value)

  • IP:

    emit(doc['clientip'].value)

  • Composite:

    if(doc['geo.dest'].value == doc['geo.src'].value) {
        emit('english', 'equals');
        emit('spanish', 'es igual');
        emit('french', 'équivaut à');
        return;
    }
      
    emit('english', 'does not equal');
    emit('spanish', 'no es igual');
    emit('french', 'n\'est pas égal');

• Create options list controls on these new fields
• Ensure that they work as expected, including chaining and validation.

Flaky Test Runner

Checklist

• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for cross-browser compatibility

For maintainers

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

[Heenawter]

With the old "fake" cache, because it relied solely on data view IDs, adding a runtime field required a hard refresh in order to get this new field to show up in the field list for creating/editing controls. By using Lodash's memoize instead, I can force the cache to update when the fields change, so a hard refresh is no longer required when runtime fields are added.

[Heenawter]

Since the runtime field tests also require adding data (but in a slightly different way), I decided to encapsulate the relevant data addition/removal in to the respective runtime field and exists query test suites rather than doing it all as part of the main test suite setup.

[elasticmachine]

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

[nreese]

nit - How about renaming loadFieldRegistryFromDataViewId -> loadFieldRegistryFromDataView?

[Heenawter]

Oh yup, good catch! I changed it to take the data view instead of the ID so that I could get memoization to work, and I forgot to update the name to reflect this change 👍

Fixed in b1fa3e1

[nreese]

LGTM
code review, tested in chrome

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: b1fa3e1

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
controls	473.5KB	473.9KB	+344.0B

Unknown metric groups

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	59	65	+6
osquery	108	113	+5
securitySolution	441	447	+6
total			+19

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
fleet	67	73	+6
osquery	109	115	+6
securitySolution	518	524	+6
total			+20

History

• 💚 Build #87704 succeeded 7c5f88c
• 💚 Build #87145 succeeded 57665cde0895ba91e10e24f2abc00e4ed01aa3b3
• 💔 Build #87083 failed cb917bce1ba4a6a67092b315d6dbb26c8dfad5b6
• 💚 Build #86864 succeeded 2dc599c34510b0ca142a6c0d7de7617c373a726b
• 💚 Build #86839 succeeded 9fed8e74242eb8efd56144ba828a76c715163a33

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

cc @Heenawter