[Cases] Add custom fields: List type

[Zacqary]

Summary

Closes #176491

Adds the List custom field type to Cases. Also makes some changes to the custom field configuration type system to handle the new features added in this field type.

The List field type creates a <select> dropdown with a set of options determined by the custom field's configuration. Options are defined as { key: UUID, label: String }.

When the user selects a value, it is saved to the case with the schema { key: Custom Field UUID, value: Option UUID }. The option's label is fetched at runtime by the UI from the custom field configuration, and displayed. This is a deviation from the research issue proposal, which specced a schema of { key: ${Field UUID}.{Option UUID}, label: Option Label }. Engineering this turned out to require major changes to the form UI library and the API transformation libraries, and it's a less drastic change to simply convert the key to a label when displaying the field.

Option labels can be renamed for free using this new schema, since the UUID is the only thing stored in case saved objects. We don't need to create a new issue to add renaming support.

This PR also allows List fields to be filtered. This required a change from using static filterOptions in custom field configurations to a dynamic getFilterOptions function. The Toggle field was updated to use this new dynamic function.

Known Issues

Due to elastic/eui#8027 drag-and-drop on the new <OptionsField> doesn't correctly render the current draggable element inside the flyout. EUI is aiming to fix this before 8.16.

Checklist

• 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

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[Zacqary]

/ci

[Zacqary]

/ci

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 096fc7c

Failed CI Steps

• FTR Configs #13
• FTR Configs #21

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
cases	812	822	+10

Async chunks

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

id	before	after	diff
cases	491.4KB	494.3KB	+2.8KB

Page load bundle

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

id	before	after	diff
cases	151.1KB	160.8KB	+9.7KB

History

• 💔 Build #239167 failed 2d986f4
• 💔 Build #238916 failed b0cdbfb
• 💔 Build #238828 failed 1f3b3d1
• 💔 Build #238480 failed c1d2552
• 💔 Build #237817 failed cd00f54

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