[Meta] New Markdown Component

[timductive]

We should simplify the multiple markdown experiences in Kibana Analytics (Dashboard, TSVB) into one core experience.
Additionally, in order to make Lens the preferred visualization editor we need to convert legacy visualization, TSVB markdown to Lens.

Tasks

Preview Give feedback

1. [TSVB] Better handling of markdown links with spaces #161062
   Feature:Lens Feature:TSVB Team:Visualizations enhancement impact:medium +5
2. Custom markdown/handlebarsjs helpers #149947
   Feature:TSVB Team:Visualizations enhancement impact:low +4
3. [TSVB]: Explore additional HTML editing in Markdown visualization #117559
   Feature:Lens Team:Visualizations enhancement impact:low +4

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[elasticmachine]

Pinging @elastic/kibana-visualizations (Team:Visualizations)

[teresaalvarezsoler]

Closing this issue as all the sub-issues are closed as not planned. We have another meta issue to figure out deprecation of TSVB in general #198136

[Heenawter]

We also have #188910 and #188911 for adding a new, more useable markdown panel (building on top of @ThomThomson's POC) 👍

[markov00]

@Heenawter thanks, but I believe we still need a markdown panel that can be enhanced by ESQL queries or other data processing.
This is the main reason on why TSVB is still used.
We should definitely discuss together to avoid building multiple markdown experiences, one only for text and another with text + data.

[Heenawter]

We still need a markdown panel that can be enhanced by ESQL queries or other data processing

@markov00 This is definitely an enhancement that could be added to the new markdown embeddable we plan to build. Either that or, if the vis team already has plans for this type of markdown and wants to own it, we could discuss how to implement the features we want into that. cc @jb1b84 @teresaalvarezsoler @nreese

We should definitely discuss together to avoid building multiple markdown experiences,

++ to this

[teresaalvarezsoler]

Yes, let's add as requirements for the new Markdown to add data (using ES|QL) and configure some basic CSS. These two things should be enough to replace the TSVB Markdown in the future.