Adds row click trigger for Lens table drilldowns

[streamich]

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

Closes #78289

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
• Documentation was added for features that require explanation or tutorials
• 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)

For maintainers

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

---

Release note

A ROW_CLICK_TRIGGER UI Actions trigger was introduced for Kibana dashboard tables. In this first iteration the row click trigger is added to Lens embeddable for datatable expression renderer.

URL drilldown makes use of the row click trigger to allow users to attach URL drilldowns to that trigger:

When row click trigger is picked as the trigger for a drilldown, user can use new event scope variables: event.values, event.keys, event.columnNames and event.rowIndex.

Once one or more row click triggers are attached to a lens datatable, a new "Actions" column appears with a context menu for each row.

[flash1293]

Looks pretty good, left a small nit about typing.

Also, I'm not sure whether it's a bug or not, but I configured this drilldown url: https://google.com/{{event.values}}/{{event.columnNames}}/{{event.keys}}/{{event.rowIndex}}/{{panel.id}}/{{panel.title}}

It doesn't give me any actions in the table, seems like something is wrong with it but it looks like it should work fine.

Also, it's pretty hard to get the template right because there are so many clicks between editing the template, testing it and editing it again - save drilldown, close flyout, save dashboard, edit dashboard, context menu, edit drilldowns, select correct drilldown. Pretty annoying because you there's no way to "preview" the values you will get before actually using them

[jbudz]

operations optimizer limits LGTM

[spalger]

Bundle limit change is just a shift of 36.5k between bundles, LGTM

[flash1293]

Looks almost ready to merge to me, left some nits

[flash1293]

LGTM from Lens side, didn't run the code again

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 1d16a78

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
embeddable	101	102	+1
lens	460	461	+1
uiActions	29	30	+1
uiActionsEnhanced	140	120	-20
urlDrilldown	8	28	+20
total			+3

Async chunks

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

id	before	after	diff
lens	1012.6KB	1017.9KB	+5.4KB

Distributable file count

id	before	after	diff
default	47129	47889	+760

Page load bundle

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

id	before	after	diff
embeddable	226.1KB	228.3KB	+2.2KB
expressions	189.9KB	190.3KB	+478.0B
lens	53.2KB	53.7KB	+534.0B
uiActions	65.3KB	69.4KB	+4.1KB
uiActionsEnhanced	304.4KB	267.3KB	-37.0KB
urlDrilldown	13.9KB	50.6KB	+36.8KB
visualizations	169.0KB	169.1KB	+64.0B
total			+7.0KB

History

• 💚 Build #93919 succeeded 1d16a78
• 💚 Build #93905 succeeded 3e370f9
• 💚 Build #93612 succeeded e4ac69d
• 💔 Build #93571 failed 9800600
• 💔 Build #93566 failed 919aa56

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