Migration distlock acquisition fails to catch status

During scheduling a migration, we attempt to acquire the local distlock for the namespace. This acquisition isn't exception-safe – in particular, in can throw LockBusy.

We don't attempt to catch this exception (unlike in the next dist-lock acquisition, where we check the status then just return).

As a result of this uncaught exception, the balancer thread will crash, terminating the whole process.