Monitoring locking

### What feature do you want to see added?

It would be useful to have such type of lockable resource, that is locked/unlocked once by some job and other jobs are only monitoring resource's state and wait until it is unlocked, but not locking it themselves.

For example when running job, which perform HTTP Server maintenance, it locks Server resource and all other jobs, which use that Server are stopped until maintenance is finished.

### Upstream changes

_No response_

The issue does not name files, tests, or entry points. Start by reviewing the plugin's existing lockable-resource behavior and how jobs wait for resources; done means one job can lock and unlock a resource while other jobs monitor its state and wait without acquiring the lock themselves.

Written by the indexing model from the issue text.