Resolve "Hashed storage: extend "Enable hashed storage for all new projects" to "for all new and renamed projects""

What does this MR do?

Before: If hashed storage is enabled then all the new projects will be created in it.

After: The same + extended to every renamed project.

Are there points in the code the reviewer needs to double check?

Yes, we have to create an EE counterpart for this MR. Once it's reviewed I will do that!

Why was this MR needed?

See the #46940 (closed) issue

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Conform by the code review guidelines
  • Has been reviewed by a UX Designer
  • Has been reviewed by a Frontend maintainer
  • Has been reviewed by a Backend maintainer
  • Has been reviewed by a Database specialist
• Conform by the merge request performance guides
• Conform by the style guides
• If you have multiple commits, please combine them into a few logically organized commits by squashing them
• Internationalization required/considered
• End-to-end tests pass (package-and-qa manual pipeline job)

What are the relevant issue numbers?

Closes #46940 (closed)