Improve design in repository configuration area regarding component scanning [DATACMNS-493]

Oliver Drotbohm opened DATACMNS-493 and commented

In the course of fixing DATACMNS-492 it became clear that currently the implementation of scanning for repository components is spread amongst two separate places (the RepositoryConfigurationSourceSupport - repository interfaces - as well as the RepositoryBeanDefinitionBuilder - for custom implementations).

This requires both the ResourceLoader and the Environment to be handed into both components. This should be unified into a single place by either moving the scanning for custom implementations into RepositoryConfigurationSourceSupport as well or by moving the entire scanning into RepositoryBeanDefinitionBuilder

Issue Links:

• DATACMNS-492 Scanning for custom repository implementation classes does not use Environment

Referenced from: commits https://github.com/spring-projects/spring-data-commons/commit/ec49499e50ea3a282ed2031a467c5b02189ad130, https://github.com/spring-projects/spring-data-commons/commit/3e4e9c2b2c6f88403b1e2bc9032b1578a588bc43