Tweak the timeouts in the getMore section of the test, and cap the
number of jobs resmoke.py uses in evergreen at the number of available
cores on the machine.
This restores the behavior from 2.6 to interrupt server-side javascript contexts, but doesn't fix
the existing bugs with it due to multiple javascript scopes being associated with a single opId and
opIds changing between getMore calls.