ISPN-4435 CacheNotifierImplInitialTransferDistTest test instability part

2

* Changed to not notify listener a second time

https://issues.jboss.org/browse/ISPN-4435
It would technically involve both, but in this case the big thing is an empty segment.  The segments with values aren't notified right away like empty segments, instead they would be notified after they are iterated on using the iterator.  This is require to do the proper event tracking so we don't get duplicates etc.

The issue that caused this is the following:

1. Request for initial state begins
2. Remote request is sent and retrieves all of it's segments (note that the main thread doesn't send the local segment retrieval yet - since no thread can run it)
3. The remote segment starts a local thread iteration since it sees no one is running it.  This means it completes the iteration and sets the values in the iterator
4. The iterator hits the segment while iterating that we are looking for and causes it to block.
5. The remove is ran removing the value from the cache.
6. The other local iteration begins and doesn't see the value closing out the segment.

This is why it saw 9 notifications instead of 11.  Both of which are valid values depending on what time they iterate on.  The problem is the test was always expecting 11.