UX: Display a welcome walkthrough when opening a Workspace for the first time
MR: Pending <!--The first line of this issue description must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, 3. If there are multiple MRs: ``` MRs: - <MR 1 link with trailing +>` - <MR 2 link with trailing +>` - ... ``` 4. `MR: No MR` ...and the first description line of the MR should be `Issue: <Issue link with trailing +>` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#relationship-of-issues-to-mrs--> ## Description As a workspace user, I want to see a walkthrough that helps me to get started on using Workspaces similar to the one displayed for the Web IDE: ![web_ide_walkthrough.png](/uploads/54bb09561ee6e1154f76597bd98bd273/web_ide_walkthrough.png){width="1312" height="632"} ## Acceptance Criteria - [ ] Display the Walkthrough only the first time that the user opens a Workspace. - [ ] The walkthrough has links to the Workspaces user documentation. - [ ] TODO: Specify other content should appear in this walkthrough. ## Technical Requirements TODO: Fill out or delete (optional) \[If applicable, please list out any technical requirements for this feature/enhancement.\] ## Design Requirements TODO: Fill out or delete (optional) \[If applicable, please provide a link to the design specifications for this feature/enhancement.\] ## Impact Assessment TODO: Fill out or delete (optional) \[Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.\] ## User Story TODO: Fill out or delete (optional) \[Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.\] <!--Replace with other type, e.g. bug or maintenance, if appropriate--> <!--Replace with other subtype if appropriate--> <!--By default, all issues start in the unprioritized status. See https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/#-planning-process--> <!--For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase-->
issue