Custom volumes and volumeMounts in Remote Workspaces
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Enable Remote Workspace administrators to define a set of volumes and volumeMounts to be added to remote workspaces. #### Use Cases 1. As a workspace administrator, I want to automatically expose datasets to my developers using a Persistent Volumes. 2. As a developer, I want my workspace to be pre-configured with necessary access to datasets mounted directly into my workspace. 3. As a workspace administrator, I want a custom CA certificate chain to be mounted into all remote workspaces. #### Acceptance criteria - [ ] Administrators can specify a list of required volumes and volumeMounts through agent configuration. <!-- 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