Improve lock held message in client output

When a user tries to kill a job that's locked by an in-progress/failed update, the error message is confusing. It should clearly state that the problem is an update lock, and how to release that lock.