Handle when interior callable or runnable is a VirtualCallable or VirtualRunnable, and being run within a test scheduler
Changed the name of this wrapper to be more accurately named.  This is a wrapper for the java.util.concurrent.ScheduledExecutorService to implement the commonly used threadly interface SubmitterSchedulerInterface (so that if you desire you don't need to use threadly's thread pool implementation).
Fix for IllegalArgumentException if expected parallism is > the max thread count.  There is no need to force the parallism to be lower than the thread count (although it does have limited value)
Renamed again, It's a longer name, but it is much more descriptive IMO
Updated README with most recent rename
Much more complete update to README based off Threadly's modern features and names.
This can be final
Lot more descriptive javadoc as to what this is actually doing.
More javadoc clarification
Fix for check style warning
Remove protected stuff from the javadocs
Merge remote branch 'origin/unstable_staging' into unstable_staging
Primarily javadoc improvements.  Making classes which have no use outside of their package have the default visibility instead of public (thus excluding them from javadoc).

Also moved the ConsumerIterator from an inner class to a top level class.  There is no reason to hide this inside the DynamicDelayQueue.
Merge branch 'master' into experimental-more_concurrent_scheduler
While looking at issue #39, it was found that shutdownNow also did not folow java.util.concurrent.ExecutorService definition.
This commit fixes the shutdownNow case, but does nothing for the shutdown() case yet.
Reduced code duplication by using the RunnableFuture inside the PriorityScheduledExecutorServiceWrapper
RunnableFuture is an implementation of java.util.concurrent.RunnableFuture
Pull this inner class out to a top level class file that is a bit more generic.  Right now it is only used here, but we may want to expand that.
Spacing change and renamed this file...not sure if I want this to be an implementation or an interface yet
Cleaned up interfaces and implementations with futures.  I also renamed RunnableFuture to RunnableFutureImp (for the time being) to avoid the confusing from java.util.concurrent.RunnableFuture