Add support for API consumer information as artifact metadata

[simonnepomuk]

Feature Description

In my work environments I often face the problem of not knowing which service depends on which API. This then leads to making rounds with development teams or scrolling through outdated confluence documentation. It would be nice to have one central place where I can look up dependencies between the services, so I can know how big of an impact breaking changes would have.

Proposed Solution

Add a list of consumers as a field on the metadata of an artifact. APIs and dependencies can then be managed in a central place.

Additional Context

This could also be integrated nicely in an automated workflow with the maven plugin. E.g. when pulling an artifact with the maven plugin, you can pass the option to add the pulling application as a consumer to the artifact metadata.