What does this MR do?
It makes sure the
RenameReservedPaths migrations don't try to move projects on disk that are using hashed storage.
When this is the case, the move wouldn't have succeeded and logged the error. But since this is not really an error, it's better to skip the move when hashed storage is enabled.
Does this MR meet the acceptance criteria?
Changelog entry added, if necessary
Tests added for this feature/bug
Has been reviewed by Backend