If the user doesn't configure a metadata repository version and doesn't configure a specific URL, we should download the metadata repository from Maven Central (or, more specifically, from the repositories declared in the build).

Unfortunately, there are a couple places where the metadata repository service can be registered, and one of those places doesn't set the correct URL.

I think this comes from a merge conflict which wasn't done properly, as the service initialization should have been done in a single method called from 2 places instead.