Clean up registration of repositories involving classloading checks on registration [DATACMNS-1619]

Oliver Drotbohm opened DATACMNS-1619 and commented

DATACMNS-1617 unveiled that we apparently inadvertently keep repository interfaces that cannot even be loaded around for inspection (see RepositoryConfigurationExtensionSupport.getRepositoryConfigurations(…) and {….loadRepositoryInterface(…)}}). They effectively cannot be used and will cause errors downstream upon closer inspection, which is probably one reason that the error has not been discovered yet.

Apart from avoiding to keep those around in the initial configuration phase, it creates the impression, we'd adapt to classpath errors in the configuration which we don't do and don't want to

Issue Links:

• DATACMNS-1617 Automatically drop repository interfaces that cannot be loaded fully