Add panel selecting a DS as onboarding experience

[natellium]

Scope

Continuation of #58218. Defines what's needed for the Datasource connection feature to go GA.

Requirements & Caveats

For G10 Under FF: First stable version to gather feedback and data

Beta Give feedback

1. Do a PoC to test if having a blocking modal when creating a panel increases engagement #65049
   area/datasource area/panel/edit internal +3
   
2. Datasource onboarding: Onboarding page won't show when default datasources are set up #62343
   area/datasource area/explore onboarding +3
3. Open the DS picker modal when the user is adding a visualization into a Dashboard #65585
   0 of 1
   area/datasource area/panel/edit +2
   
4. The panel still added into the dashboard after discarding changes while editing #65588
   area/panel/edit internal onboarding type/bug +4
   
5. Add Rudderstack events to the different items #65833
   area/instrumentation onboarding +2
   
6. Panel edit plugin not found: undefined on a new dashboard screen #66659
   area/dashboard internal type/bug +3
7. Check permissions before showing "Add new data source" #67239
   internal +1
   
8. Direct "New Datasource" button to connections page if toggle is enabled
9. Enable FF in Canary

Feedback G10-preview: Bugs or improvements

Beta Give feedback

1. Update Grafana built-in DS to describe what each of them does #67700
   area/datasource area/panel/edit internal type/bug +4
   
2. When showing the onboarding, modifies the URL adding a history entry #67894
   area/panel/edit onboarding type/bug +3
   
3. Advanced DS picker is open when re-rendering the query editor #67709
   area/dashboard area/panel/edit +2
4. Navbar resets to dashboard state when opening the advanced DS modal picker #67805
   area/panel/edit type/bug +2
   
5. Make the DS modal works for mobile #66917
   area/datasource area/panel/edit internal kind/enhancement +4
   
6. Refactor the flow/detection of first panel created in a dashboard #66946
   area/panel/edit internal kind/enhancement onboarding type/bug +5
   
7. Update the E2E plugin repository supporting the new flow

Docs

• Product DNA
• Figma
• FigJam Critical User Journey
• Delivery plan

[thanos-karachalios]

After discussion with @ivanortegaalba and @Ijin08

• Not replicate OSS solution flow[depending POC outcome]
• Follow flow through standard screens: "Empty State Dashboard" New empty dashboard screen #60108 , "DS selection modal" Data source selector #62083 and "Collections Page"
• Current issue with the suggested solution, is user flow breaks with the initial dashboard creation flow. @ivanortegaalba to check feasibility of user journey continuation through Connections page flow (Check FigJam Option 1 Flow)
• If the above is not feasible through the POC, we are not effectively solving the onboarding of new users. In such case @Ijin08 creates a screen similar to OSS solution. This is applicable only on first time dashboard author as described in Product DNA doc.

Although an inline/in-context DS config would provide a new perspective scoping the solution I don't think we can prioritise it towards G10 release given our planned and committed items cc @natellium

[thanos-karachalios]

After discussion with @ivanortegaalba and @Ijin08 and based on the outcomes of POC:

• @Ijin08 creates a screen similar to OSS solution. This is applicable only on first time dashboard author as described in Product DNA doc. Some preliminary designs exist when initially scoping the feature between @thanos-karachalios and @ivanortegaalba for Patrick to start with. Thinking of time to G10 we can exclude suggested dashboards out of scope for now.

• Review the appropriate wording or text in the CTA of modal in creating new viz in existing dashboards.

• @Ijin08 to create flows for first time authors and behaviour of modal in existing dashboards

Inline/in-context DS config would provide a new perspective scoping the solution and is best to think about it overall holistically post G10

[thanos-karachalios]

After discussion with @ivanortegaalba @dprokop @natellium and @torkelo and based on the outcome of POC

• Follow flow through standard screens: "Empty State Dashboard" New empty dashboard screen #60108 , "DS selection modal" Data source selector #62083 and "Collections Page"
• inline/in-context DS config is not currently in scope based on POC outcome
• OSS screen will be replaced by the same flow.
• @Ijin08 to align with @ivanortegaalba on flow details and possible design changes in modal in OSS case