<!--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=477965) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=477965) </details> <!--IssueSummary end--> MR: Pending ## Description As gitlab-org/gitlab#516058+ is handling renaming the model and table associated with namespace cluster agent mappings, we should also update the mutations to reflect these changes and be consistent. We need to rename the GraphQL mutations on namespace agent mappings `NamespaceCreateRemoteDevelopmentClusterAgentMapping` and `NamespaceDeleteRemoteDevelopmentClusterAgentMapping` to `NamespaceCreateClusterAgentMapping` and `NamespaceDeleteClusterAgentMapping` Related to category rename: https://gitlab.com/gitlab-org/gitlab/-/issues/472761+, and adding new auth mapping controls: gitlab-org#16485+ ## Acceptance Criteria - [ ] Follow the [graphQL deprecation process](https://docs.gitlab.com/api/graphql/#deprecation-and-removal-process) on the old mutations (referencing the incoming new mutations as substitutes) - [ ] Introduce the mutations with the new names <!-- 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 -->