Lock messages could be clearer

Somewhat related to #154, when locking multiple resources, it is sometimes not clear why the job canot continue, for example:

```
23:40:09 Trying to acquire lock on [{XXX-guitest},{Label: kubernetes-guitest, Quantity: 1}]
23:40:09 Resource [XXX-guitest] did not exist. Created.
23:40:09 Found 0 available resource(s). Waiting for correct amount: 1.
23:40:09 [{XXX-guitest},{Label: kubernetes-guitest, Quantity: 1}] is locked, waiting...
11:09:27 Lock acquired on [{XXX-guitest},{Label: kubernetes-guitest, Quantity: 1}]
```

(Bonus: If the situation changes, but the lock is still held, because now other resources are missing, log this too)