[Controls] Add ESQL control types to options list

[Zacqary]

Summary

Part of #227062

This adds types for ES|QL control properties and API methods to the options list control factory in preparation to unify the factories. It does not actually yet make the control function with ES|QL data sources or variables, but lays the groundwork for adding this functionality in a second PR.

• Options list control now optionally accepts all the properties in ESQLControlState as a possible input state. The input state must now be either ESQLControlState or DefaultDataControlState.
• The options list control and component APIs now publish esqlQuery$, esqlVariable$, and esqlControlType$. esqlVariable$ is an ESQLControlVariable derived from the ES|QL control's variableType/variableName, and the other two subjects are simply renamed properties to reduce ambiguity downstream in the control factory.
  • esqlVariable$ will publish from the control API and be read by the control group. This is how current ES|QL controls already publish their variables and make them available to the dashboard. In this PR, it will always publish undefined and therefore do nothing.
  • esqlControlType$ can be used to determine whether to fetch available options list suggestions, or to pull them from the availableOptions input state
  • esqlQuery$ can be used to fetch available options if the control type is VALUES_FROM_QUERY
• Options list suggestions data requests to be passed to fetchAndValidate now have types for possible ES|QL requests. See this part of the initial draft unification PR for an example of what this enables us to do.
• An ESQL state manager has been added to the options list factory, even though it's not fully implemented yet. This generates all the needed publishing subjects and allows the component and control APIs to pass the new type checks.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[Zacqary]

The fieldName subject is only used in the UI component to generate aria labels and such. Because ES|QL controls won't have a fieldName this is being changed to displayName and derived within the factory from whichever descriptive properties are available.

The default is now title if defined, which I think was an oversight in the initial implementation.

[Zacqary]

We don't pull availableOptions into the state here, the options list already has an availableOptions state and those get derived within fetchAndValidate.

The follow-up PR will apply a static values control's availableOptions instead of fetching data.

[Zacqary]

This type was unused

[nreese]

Lets rename OptionsListDataControlState to 'OptionsListDSLControlState' since data has little meaning and is very ambiguous.

[elasticmachine]

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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 220f144

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
controls	396	397	+1

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	101	95	-6

Async chunks

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

id	before	after	diff
controls	485.0KB	485.4KB	+328.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
controls	15	17	+2

Unknown metric groups

API count

id	before	after	diff
controls	105	99	-6

History

• 💔 Build #337038 failed 978a9a6
• 💚 Build #333741 succeeded 9c0f2eb
• 💔 Build #333392 failed 86f31bf
• 💔 Build #333367 failed fd6382a
• 💔 Build #333334 failed 5318597

[nreese]

kibana-presentation changes LGTM - thanks for breaking these type changes out into its own PR
code review only

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233126 locally
cc: @Zacqary

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233126 locally
cc: @Zacqary

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233126 locally
cc: @Zacqary

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233126 locally
cc: @Zacqary

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233126 locally
cc: @Zacqary

[adcoelho]

Ping @Zacqary , this needs to be backported.

[Zacqary]

💚 All backports created successfully

Status	Branch	Result
✅	9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation