cachedThreadPool polling

When longer-running jobs have multiple pushes, it will cause blocks on other projects' github triggers.  

The culprit appears to be a combination of a job requiring a lock on its workspace to poll (fast-remote polling is not ideal) during a running build, and the singleThreadExecutor.  

By changing to cachedThreadpool, no projects get held up and the system is not overloaded.