SPBucket: Prevents empty lastChangeSignature scenarios

There are several flows that could, potentially, lead to multiple calls to `SPWebSocketChannel :: allVersionsFinishedForBucket` method.

If that happens, we could, potentially, end up with a SPBucket instance with a nil `lastChangeSignature field.

Fixes #325 

If this is actually possible, do we check places where we go into this state to make sure we don't start two indexing/re-indexings concurrently?