Refactor project destroy services

What does this MR do?

In preparation for !22672 (merged), we need to refactor a little bit the Projects::DestroyService. At the moment, this service has hardcoded the repositories it has to delete and the service has many responsibilities.

In this MR, we refactor the existing Projects::DestroyService creating three services just for dealing with repositories and extracting this functionality from this service.

We also split some of the existing functionality. The current destroy service delete things but also is able to rollback stuff. We can have this functionality in a different service.

Does this MR meet the acceptance criteria?

Conformity

• [ ] Changelog entry
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content