Feature: Support for maven repository as a source for concord repository

[amithkb]

Currently, Only git is considered as a repository source for Concord workflows. In scenarios where git is unavailable or teams adopting CIOPS approach for developing Concord workflows, support for a build or a package registry as a source will be necessary.

• [ ] Support for mvn:// as the url source for concord repository
• [ ] Support for triggers on publish of an artifact(Concord workflows) to the maven repository

[ibodrov]

Support for mvn:// as the url source for concord repository

A good starting point is RepositoryProvider

There are already multiple RepositoryProviders, it should not be too hard to add one that is backed by DependecyManager.

[ibodrov]

Support for triggers on publish of an artifact(Concord workflows) to the maven repository

If the repository supports basic webhooks with JSON payload (e.g. Nexus) then it should be possible to consume such events using Generic Triggers