Revisit terminology around workspace containers

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 Refactor workspaces component-related code and ... (!174589 - merged) should be addressed:

• @Saahmed started a discussion: (+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: !174589 (comment 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.]