Decision: Decide whether Workspaces domain should use YARD @raise annotations or not
MR: Pending
<!-- NOTE: For context on MR heading, see:
https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/index.html#relationship-of-issues-to-mrs
-->
## Description
For the Workspaces domain/bounded context, do we want to use the `@raise` annotation in YARD, or just `@param` and `@return`?
This issue is a followup to this related discussion: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/183440#note_2381131817
<!-- 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
TODO: Fill out (required)
- [ ] [Describe what must be achieved to complete this issue.]
- [ ] [If applicable, please provide design specifications for this feature/enhancement.]
- [ ] [If applicable, please list any technical requirements (performance, security, database, etc.)]
## Implementation plan
TODO: Fill out or delete (optional)
[Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.]
<!-- NOTE: Feel free to expand with more sections and headers as needed -->
<!-- DO NOT TOUCH BELOW -->
issue