Robot timing errors

[haysmark]

The doh.robot schedulers assume real-time processing. The reality is that people run tests on clouds, virtual machines, slow computers, and slow browsers where real-time processing is not guaranteed. We should try to adjust the schedule as robot actions fire to compensate for unexpected lag.

[haysmark]

Refs #11982. Modify doh.robot scheduling of typeKeys and mouseMove to compensate for unexpected delays.

[haysmark]

Robot jar.

[Douglas Hays]

Some of the sequence durations are still being doubled due to a new sequence call coming in just before the previous duration setTimeout fires. I suggest the following sequence function replacement:

var currentTime = (new Date()).getTime();
if(currentTime > (doh.robot._time || 0)){
        doh.robot._time = currentTime;
}
doh.robot._time += delay || 1;
setTimeout(f, doh.robot._time - currentTime);
doh.robot._time += duration || 0;

[Douglas Hays]

(In [23255]) Fixes #11982. Proxy commit for haysmark (IBM, CCLA). Refactor sequence function to avoid incorrect delays. Change robot applet to adjust initial key delays if key processing is going unusually slowly.