Hashed storage sends a Geo repository renamed event

Summary

When renaming a project on a Geo primary with hashed storage enabled, the secondary receives a Geo::RepositoryRenamedEvent.

Steps to reproduce

Rename a repository with hashed storage enabled, at least, once https://gitlab.com/gitlab-org/gitlab-ce/issues/38202 is resolved.

What is the current bug behavior?

Geo secondary receives a repository renamed event, and attempts gitlab_shell.mv_project(same_path, same_path) as a result. Fortunately, this will fail - the destination already exists, and gitlab-shell checks that - but I wonder if we can skip the move entirely.

What is the expected correct behavior?

We shouldn't be attempting mv_project at any time for hashed storage repos or wikis.

Possible fixes

https://gitlab.com/gitlab-org/gitlab-ee/blob/v10.0.0-rc4-ee/ee/app/models/ee/project.rb#L477

/cc @brodock