[TSVB] Visualize runtime fields

[alexwizp]

Closes: #82438

Release Notes

This PR adds support of Runtime Fields for TSVB visualization. Since Kibana supports this type of fields only through the creation of a Kibana Index Pattern,Runtime fieldswill be available on the indexpattern mode. More information here

Testing Notes

1. Create a new Runtime Field
   • Navigate to Stack Management -> Index Patterns -> { some index pattern e.g. kibana_sample_data_ecommerce};
   • Press Add Field button;
     
   • Press Save
2. Create a new TSVB visualization
3. Create new Aggregation with created Runtime Field
   

Expected result:

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[VladLasitsa]

LGTM

[alexwizp]

@elasticmachine merge upstream

[stratoula]

@alexwizp although I am on the string mode, I can still see the runtime fields and create visualizations with them.

[stratoula]

Moreover markdown editor breaks

Uncaught TypeError: Cannot read property 'set' of undefined
    at convert_series_to_vars.js:35
    at Array.forEach (<anonymous>)
    at convert_series_to_vars.js:18
    at Array.forEach (<anonymous>)
    at convertSeriesToVars (convert_series_to_vars.js:17)
    at MarkdownEditor.render (markdown_editor.js:58)
    at finishClassComponent (react-dom.development.js:18470)
    at updateClassComponent (react-dom.development.js:18423)
    at beginWork$1 (react-dom.development.js:20186)

[stratoula]

Also, we don't respect the format of the field. I have created a keyword runtime field with uppercase formatting but still my value appears lowercase.

For example on the area XY chart it is respected:

Moreover if I create a TSVB viz with a runtime field and then delete it, my visualization doesn't appear as broken but with no results found.

I think that it should work as the other visualizations, it should notify the user that this visualization uses a field that doesn't exist anymore but still allow the user to edit this.

[alexwizp]

@elasticmachine merge upstream

[alexwizp]

@elasticmachine merge upstream

[stratoula]

@elasticmachine merge upstream

[alexwizp]

@elasticmachine merge upstream

[stratoula]

Works fine, found some bugs though:

• I create a table with runtime field and although it exists I receive

• Something goes wrong when I delete two runtime fields that my visualization relies on (see comment below)

[alexwizp]

@stratoula thank you for that two broken scenarios

[stratoula]

Nice @alexwizp, I think it works great. Thank you a lot for all your effort in this PR and for addressing all comments ❤️

[VladLasitsa]

LGTM

[timroes]

@elasticmachine run elasticsearch-ci/docs

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 4f4367f
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
visualizations	84	85	+1

Async chunks

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

id	before	after	diff
visTypeTimeseries	1.6MB	1.6MB	-420.0B

Page load bundle

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

id	before	after	diff
visTypeTimeseries	109.3KB	109.7KB	+411.0B
visualizations	91.9KB	92.5KB	+669.0B
total			+1.1KB

History

• 💚 Build #118610 succeeded ab814c7
• 💚 Build #118569 succeeded af09ac3
• 💔 Build #118553 failed a579c87
• 💔 Build #118517 failed 663636c
• 💚 Build #118121 succeeded 70970b9

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

cc @alexwizp