fix(mod/lock): correct watch index to remove cpu load

The waitIndex was being pulled from the wrong node in the lock parent which caused the watch to be returned immediately. This caused a continuous stream of get/watch calls while a client was waiting for a lock.

Confirmed with @oleksiyk that this change fixes https://github.com/coreos/etcd/issues/575.

/cc @philips @xiangli-cmu