MR: Pending ## Description Revisit terminology around workspace "user" (non-init) containers - "tooling" vs "main" vs "application" vs ??? This was raised in the following discussion from !174589+ should be addressed: - [ ] @Saahmed started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/174589#note_2243936029): (+1 comment) > Question?(non-blocking) > > Out of the scope of current changes, but I wonder if we could give a definite name to the `main_component` from the devfile to decouple from `gl/inject-editor`, something like `gitlab-workspace` (most devfiles we use call it ` tooling-container` which appears misleading to me) - See also @cwoolley-gitlab response in that thread: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/174589#note_2244589922 ## Acceptance Criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [Describe another requirement needed to complete this issue.] - [ ] [Add additional acceptance criteria as needed.] ## Technical Requirements TODO: Fill out or delete (optional) [If applicable, please list out any technical requirements for this feature/enhancement.] ## Design Requirements TODO: Fill out or delete (optional) [If applicable, please provide a link to the design specifications for this feature/enhancement.] ## Impact Assessment TODO: Fill out or delete (optional) [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.] ## User Story TODO: Fill out or delete (optional) [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.] <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/#-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->