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 As part of https://gitlab.com/gitlab-org/gitlab/-/issues/409774+s, we removed agent id and user id from the workspace name (and by extension the namespace name) in favor of more user friendly names. Since this information is not available in the name anymore, we would like to put it in the annotations to help with debugging issues. <!--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 * [ ] Add following keys in the annotations * [ ] `workspaces.gitlab.com/agentk_id` * [ ] `workspaces.gitlab.com/project_id` - this will be optional if we add project-less workspaces * [ ] `workspaces.gitlab.com/namespace_id` - this is the GitLab group AKA namespace - we don't call it group_id because in the future we may support also personal namespaces. For now, this would be the `id` of the group containing the project. ## Implementation plan 1. Add annotations in [ee/lib/remote_development/workspace_operations/create/desired_config/config_values_extractor.rb](https://gitlab.com/gitlab-org/gitlab/blob/742e178b2270a2f4a6ef05eb27c471edca34fe15/ee/lib/remote_development/workspace_operations/create/desired_config/config_values_extractor.rb#L39-39) 2. Add annotations in all the relevant spec files and fixtures. <!--NOTE: Feel free to expand with more sections and headers as needed--> <!--DO NOT TOUCH BELOW-->