Make all CoreTest keys go remote

Bug is that the remote JVM loses a core to the DRemoteTask.
Launch test with 2 JVMs, and the remote only uses 3 of 4 cores.
working on a single-jvm version of coretest

replicating the i/o path for a remote task launch.
Stripped out priority queues (no help)