Add an ability to find out which mirror farm node is holding a lock for the affected repository. This helps in scenarios such as when a sync cycle is stuck and hence the other requests to sync the repository have to wait for the lock to be released. It's very hard to find out this information from the application logs as it's not clear from the logs which are related to the currently stuck sync cycle. Apart from the node, it would be useful to also get the information about the process holding the repository lock.

This is implemented, and can be used via the following endpoints:

1. Get all the repository lock owners for the syncing process
2. Get the repository lock owner for the syncing process