Fix bug with snippet refactored routes

What does this MR do?

In !20478 (merged) we refactored snippets' routes to have a single place to check if the snippet was a ProjectSnippet or a PersonalSnippet and call the proper route. Besides, in preparation for other features, we added a way to add query params automatically to all snippet routes.

Nevertheless, it seems to fail in production (#38068 (closed)). It does not fail in development or test environments. I've tried to set up the production environment caching the classes and avoid reloading but I can't make it fail.

We have tried a couple of things, but it seems the problem is the loading order of the routes.

In this MR we're renaming the routes to avoid collisions with the existing ones.

Refs #38068 (closed)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content