[Security Solution] Update CellActions field type to be FieldSpec #157243

[machadoum]

issue: #150347

Context

Some Actions need to access FieldSpec data, which is not present on the CellActions API (subTypeand isMapped). So we are updating the CellActions field property to be compatible with FieldSpec.

Summary

This PR is the first step to fix #150347.

• Updates the CellActions to support an array of data objects, each containing field (FieldSpec) and value
• Create a new SecurityCellActions component that accepts a field name and loads FieldSpec from the Dataview.

Examples

Before:

 <SecurityCellActions
      value={'admin'}
      field={{
        name: 'user.name',
        type: 'keyword',
        searchable: true,
        aggregatable: true,
        ...
      }} />

After:

 <SecurityCellActions data={{ field: 'user.name', value: 'admin' }}/>

SecurityCellActions will load the spec from the Dataview and provide it to CellActons.

CellActons now also support an of fields instead of only one field. It will be useful when rendering cell actions for aggregated data like on the Entity Analytic page. But for now, the actions are not supporting multiple values, we need to rewrite them #159480.

Next steps

We must refactor the Security Solution to get FieldSpec from the DataView instead of using BrowserFields. Ideally, we have to do that for every CellAction call so the actions can access the subType property.

• Refactor the Security Solution CellActions calls to get FieldSpec from the DataView
• Refactor data grid cell actions to get FieldSpec from the DataView
• Rewrite actions to support multiple fields and use them on the investigation in timeline (.andFilters)
• Fix CellActions component should hide ShowTopN action for nested fields #150347 using subType from fieldSpec
• Fix [Security Solution] Disable filter cellActions for unmapped fields on Alerts table #154714 using isMapped from fieldSpec

Extra information

*** Previously we were mixing esTypes and kbnTypes. For example, if the esType is a keyword the kbnType has to be a string.
Here you can check all possible ES and KBN types and here you can see the mapping between esType and kbnType

Checklist

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

[machadoum]

@elasticmachine merge upstream

[machadoum]

@elasticmachine merge upstream

[semd]

LGTM! thanks Pablo

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 7b722cb
• Storybooks Preview

Failed CI Steps

• Security Solution Tests #2
• Security Solution Tests #5
• Investigations - Security Solution Tests #4
• Explore - Security Solution Tests #2

Test Failures

• [job] [logs] Security Solution Tests #5 / Add, copy comments in different exceptions type and validate sharing them between users Rule exceptions Add comment on a new exception, add another comment has unicode from a different user and copy to clipboard
• [job] [logs] Investigations - Security Solution Tests #4 / Alerts generated by building block rules Alerts should be visible on the Rule Detail page and not visible on the Overview page
• [job] [logs] Security Solution Tests #2 / Detection response view Open in timeline "after each" hook for "opens timeline with correct query count for hosts by alert severity table"
• [job] [logs] Security Solution Tests #2 / Detection response view Open in timeline opens timeline with correct query count for hosts by alert severity table
• [job] [logs] Security Solution Tests #5 / Exceptions viewer read only "before each" hook for "Cannot add an exception from empty viewer screen"
• [job] [logs] Explore - Security Solution Tests #2 / Hover actions Adds global filter - filter out

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
securitySolution	4188	4189	+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
@kbn/cell-actions	42	43	+1

Async chunks

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

id	before	after	diff
securitySolution	10.9MB	10.9MB	+6.2KB

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	13	15	+2
securitySolution	411	416	+5
total			+7

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	14	16	+2
securitySolution	494	499	+5
total			+7

History

• 💔 Build #136147 failed 996425c
• 💛 Build #135245 was flaky 1816160d149611f277da11bcdb887b887e6ed05a
• 💛 Build #135041 was flaky 0f3f773572e9cd3ab37fb6b78f1363dfab24b3cc
• 💔 Build #134304 failed 933b0c2
• 💔 Build #133211 failed b38e323

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

cc @machadoum

[PhilippeOberti]

LGTM for the threat-hunting-investigations team

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.10	The branch "8.10" does not exist

Manual backport

To create the backport manually run:

node scripts/backport --pr 157834

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

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

[kibanamachine]

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

[kibanamachine]

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

[kibanamachine]

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