Improve workspace related data propagation from rails to frontend Vue components
<!--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>
- [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=552038)
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=552038)
</details>
<!--IssueSummary end-->
MR: Pending
<!-- NOTE: For context on MR heading, see:
https://handbook.gitlab.com/handbook/engineering/devops/dev/create/remote-development/index.html#relationship-of-issues-to-mrs
-->
## Description
Follow up from: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/194493#note_2589674584
Workspaces domain has certain parameters it would like to inject into the frontend via Rails, e.g `workspace_path` and `org_id`.
It would be preferable if we could bundle all these workspace-specific fields into a single `workspaceData` object or something similar. If possible, as well, we could look into any refactoring that would remove the need to pass these fields down into the Vue components, as this would help reduce coupling.
<!-- TODO: What kind of issue is this? Please uncomment and include one of the following:
/label ~"type::feature"
/label ~"type::bug"
/label ~"type::maintenance"
-->
<!-- OPTIONAL: Is this a feature/enhancement?
- Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.
- Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.
-->
<!-- OPTIONAL: Is this a bug? Please uncomment and include the following:
- **Current behavior:**
- **Expected behavior:**
- **Steps to reproduce:**
- **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue!
-->
## Acceptance criteria
- [ ] Pack workspace-related data into a single object to propagate to ~frontend via Rails
- [ ] If possible, refactor the code to reduce coupling involved in propogating this data
## Implementation plan
<!-- NOTE: Feel free to expand with more sections and headers as needed -->
<!-- DO NOT TOUCH BELOW -->
issue