GitLab Duo disappears in the Web IDE if you move the panel to the right side
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=462127)
</details>
<!--IssueSummary end-->
<!--This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Bug
GitLab Duo by default opens on the left side. When moving the chat to the right hand side, it docks into place. However when I close the Web IDE, and reopen it again the GitLab Duo view does not reappear.

### Workaround
To restore the panel:
- Invoke a Duo action from the context menu to reopen the view.
- Reset the view from the command palette (`SHIFT + Command + P` \> `View:Reset View Locations`)
- Enable the secondary panel via `File > View > Appearance > Secondary Side Bar`
### Possible solution
Add a button to the Web IDE's top toolbar that opens Duo Chat. The Web IDE persists the preference of moving Duo Chat to the right side panel. The UX problem is that users don't have a way of opening Duo Chat because there isn't an equivalent toolbar button to the one that appears on the left sidebar. Other tools solve this problem by adding a toolbar button, for example:
{width=1920 height=228}
<!--Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues.-->
<!--Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.-->
<!--Label reminders
Use the following resources to find the appropriate labels:
- Use only one tier label choosing the lowest tier this is intended for
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/-->
issue