Display a soultion-oriented "Choose your own journey" interstitial page

[ryankeairns]

As part of the new home page + Kibana landing project, we would like to present users with a page (upon log in) prompting them to select a solution.

This aligns with the current product marketing around the 3+1 solution set and the proposed Cloud deployment creation flow. Users will have the option to choose a solution - including the base Kibana set - or opt out and simply go to the new home page.

Technically speaking, we will likely re-purpose the existing sample data screen (also shown upon first log in) with the new content seen below:

Mockup from prototype

Prototype

https://www.figma.com/proto/537SsoT2eCzuW8MTDJps2w/Awaiting-Dev-Home-and-Kibana-Landing-Pages-MVP?node-id=4377%3A119179&viewport=9695%2C-4651%2C0.45789220929145813&scaling=min-zoom

---

Telemetry notice

As noted in the following comment from the home page issue, we need to account for the telemetry notice that currently exists on the sample data page. While the above design does not show this notice, it may be adjusted to do so or we'll have to find another location with equal prominence.

I know as part of this discussion, we also have explored adding or not adding an interstitial page. I wanted to note here, that we will need to provide notice of telemetry that is captured in the first run of Kibana. Happy to provide more details when we start building the Elastic home page out. Example below:

Originally posted by @alexfrancoeur in #25734 (comment)

[elasticmachine]

Pinging @elastic/kibana-core-ui (Team:Core UI)

[ryankeairns]

Let's put this on hold for the moment. There are discussions ongoing that could change the initial workflow to focus more so on adding data. From there, we would segue into solutions and have that prompt be informed by the type of data added in the first step.

[alexfrancoeur]

++ I agree, was going to bring this up during our sync later today. One thing that we'll have to make note of is that we need the interstitial page in the interim for the telemetry notice on first launch. That cannot go away until we have an alternative solution for self managed deployments.

[alexfrancoeur]

While there is still a lot more discussion to be had, I wonder if we can lead with Add Data here. It might be interesting to think through some concepts of what that could look like. Add data tutorials and integrations are similar in concept, so the choice we make could likely translate to both. One is just easier for the user than the other (though it happens to be in beta).

We could welcome a user and select the type of data they'd want (logs, metrics, security events) or the (top N?) actual data sources (integration, beats module, etc.). With this approach, we can keep the existing home page and augment the net new user experience. As far as work effort goes, I'd guess it's probably minimal giving the page and the logic for the page already exists. We'd simply be changing the content.

Something to think about before our sync later today (cc: @VijayDoshi @johnbarrierwilson).

[alexfrancoeur]

Based on our discussion earlier today, closing this in favor of #74690. We can re-open if we need to revisit.