[PoC] visdata interpreter function

[ppisljar]

Summary

POC for visdata interpreter function

visdata id="saved-vis-id"

it will return datatable, or throw error if saved visualization is not table based (markdown, vega, tsvb, timelion)

if visualization requires a time range prepend expression with filters | and add a time picker to workpad.

currently it has no UI, but that would probably be easy for someone from canvas team to add (should show a dropdown or sth with all saved visualziations (or maybe even the ones that don't return datatable filtered out)

PS: changing the code to not set tableOnly to true and changing functions type to render will make this render all the visualizations (also checks for data.rows should be removed)

@lukeelmers this required few hacks to visualize loader:

• we don't need dom element to get the data, also we shouldn't auto render
• hack inside visualize_data_loader to return the table and stop
• hack inside embedded visualize loader to not handle errors (custom error handler wanted)

all along the line of the new api that was discussed here: #25374

part of closing #23035

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• This was checked for cross-browser compatibility, including a check against IE11
• 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
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[ppisljar]

is there a way to pass title as well ?

[w33ble]

I'm not sure what the column object looks like here, but name should be the field name, not some unique identifier used by Kibana.

Also, don't forget to add the column type here, and just use 'string' if you can't detect that (but you should be able to based on the field mappings you have).

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[ppisljar]

with move to using expressions in visualize this will become harder,
we don't know what data powers visualization. We could still return the response from last function returning datatable type.

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request