integration: bump timeout for good path

When waiting for a watch result, we expect the good path to complete quickly
here so we don't need to time out so aggressively. (Failure noted in #1600)
In those situations we're just checking quickly that there was no watch result when one wasn't expected. Now we're ensuring that we definitely get a watch result when we expect one. But if somehow the result we get here _is_ from one of the earlier watches, then it will get caught by the checkBody on 862. Make sense?