HPCC-12633 Improve contention cost in splitter

In cases where the consumers keep pace and are waiting on the
produce side of the splitter, the cost of waiting was costly.
The change here, introduces a callback mechanism into the shared
write ahead, such that the producer [optionally] only triggers
the readers that there is something to consumer per page flush.
In the memory variety of the shared writer which blocks when it
is far enough ahead, the producer will write (and page) as fast
as possible on a async thread, and block when full.
All of this savs the cosumers, entering crits, waiting on
semaphores and waking up and re-entering crits etc. on a per row
basis when they are consuming quickly.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
Actually.. though the above is true in the putRow with a callback.
It is as it was with the non-callback putRow.

In the splitter usage now, it should always be waiting for a full rowset in readerWait.
But the current rowSet can have single rows added (via the non callback putRow) and the count can change (as it used to).

IOW it depends on the usage, so I think this code should remain unchanged..

Will still have a closer look though.