Implement LockProvider for Catalog-Service backend

[groldan]

There's no lock provider for the catalog backend. The client shall issue a request to the service, which should lock the resource on behalf of the caller service.

Moreover, given there could be several catalog service instances for HA, locks cannot be held by the service itself, so none of the current solutions would work.

Idea is to use something like spring-integration-jdbc to hold the locks on the database, but without having to keep a reference to a java.util.concurrent.Lock in memory, since lock acquire and release requests could hit different catalog service instances due to load balancing.