Chid epic of https://gitlab.com/groups/gitlab-org/-/epics/9761 ### Summary When a project under a team namespace has images in its registry, moving the team namespace is possible but moving it back under the initial namespace generates an error. Deleting all container images and tags in the Gitlab projects container registry does *not* help. This is a problem for reusing names and namespaces. If the namespace ever held images, it cannot be reused (e.g. by renaming an existing namespace to that namespace). ### Proposal Allow for the renaming of projects, even if they have container images in the project. Currently, we raise an error when the user attempts to change the project path of a project with existing container registry tags. With this new *rename repository* API endpoint, we can now allow the renaming of such projects and we use the new endpoint to update the project's resources in the container registry.  From https://gitlab.com/gitlab-org/gitlab/-/issues/420755, we can also see that the new API endpoint exposes a dry-run function and we will use this to validate that we can continue with the rename operation. A new function will be added to `GitlabApiClient` in https://gitlab.com/gitlab-org/gitlab/-/issues/423995 and this function will be the one that we will use to call the new *rename repository* API endpoint ### Roadmap This epic focuses on renaming projects. There are also the below use cases: * Allow **moving "projects"** in the same namespace" that have container repositories https://gitlab.com/groups/gitlab-org/-/epics/9761 * Allow **renaming "namespaces"** that have container repositories https://gitlab.com/groups/gitlab-org/-/epics/9762 * Allow **moving "namespaces"** that have container repositories https://gitlab.com/groups/gitlab-org/-/epics/9762