Deny Auth Requests for Rename/Move Origin Repository Requests when Geo is Enabled

Context

In order to prevent the use of registry endpoints not yet supported by Geo when Geo is enabled, we should deny requests to those endpoints in the registry authentication service.

Problem

Currently, Rename/Move Origin Repository events are not supported by Geo, so we should gate this feature until Geo support is enabled. Without this notification in place, Geo users will not be able to take full advantage of all features enabled by the next generation container registry.

Edited by Adie (she/her)