RepositoryRegistry is used for indexing context now. There is still more work to do
to move the maven dependent parts into its own projects and update the dependencies.

Signed-off-by: olivier lamy <olamy@apache.org>

Adding methods for retrieving base path information to ArchivaConfiguration
resolving paths according to the configuration entries.

CI build throws a permission denied error on the Consumer Archetype test.

Signed-off-by: olivier lamy <olamy@apache.org>

Not finished yet, but uses the maven index service via spring dependency injection
Moving some maven specific classes to subpackages

Combining the indexer api and repository api into archiva-repository-api
They have bidirectional dependencies so they are put together in one module.

Adding new classes for a generalized indexer api that will be used for interfaces
and implementation independent tasks.

[MRM-1964] Step to move all indexing features behind archiva API

Adding content provider service that creates repository content instances
remove direct access to the repository content instances.

Removed reference to module in pom.xml that does not exist.

Using the repository api and RepositoryRegistry for repo access

Using the repository api where necessary.

Switching to the repository registry to retrieve repository data.
Indexing is currently kept in the admin part, but will be moved in the future
to the registry.

Adding unit tests for the registry.
Fixing some uri issues.
Removing dependency to consumer to break circular dependency