Bugfix - tests failing on slow responses

[krisgesling]

A number of tests are currently failing for the Wiki Skill, caused by the delay in responding exceeding the default 10 second Voight Kampff Step timeout.

This adds a custom wait while speaking step to delay the start of the final mycroft reply should contain step for each test. An additional 3 second sleep was added to this to ensure some delay occured given the Docker runs use a dummy TTS and hence wouldn't pause.

This is intended to get the VK tests passing in the short term. More thought needs to go into the best way to handle this going forward to make the test suite more robust.

We also need to investigate ways to speed up the response time from the wikipedia service. A user shouldn't need to wait > 10 seconds for an answer. Options are to switch libraries or reduce the search calls. Currently for a single search we can make up to 3 requests to wikipedia as we:

1. List possible pages
2. Fetch two line summary of most likely page.
3. If too long, re-fetch one line summary

[forslund]

As I recall it step 3 was added since the method used to cut down the number of lines produced bad results

I quick couple of tests using "George Washington":

Search step takes ~0.8 seconds

Summary retrieval options

• 2 Summary requests in series: 2.65 sec
• 2 Summary requests in parallel using concurrent.futures.ThreadPoolExecutor: 1.8 seconds
• 1 Summary request and cutting out the first sentence: 1.6 seconds

I also did an experiment with 2 sequential summary calls using "hyper" for http2 usage getting the time down to ~1.2 seconds (this could be a couple of factors since I had to do some edits to the wikipedia module code)

[forslund]

Also tested and working well. (though the speed of the wiki calls are much higher now than before today so there is no issue for me)