Continuing problems with the pipe... (Add small sleep to no process failure retries)

Dear SQLClient,

In our sessions together we have made significant progress in understanding your issues with finding no processes at the end of your pipe. However, in reviewing your records on the CI server I notice that you are occasionally still confused about what is in your pipe. I recommend we extend your therapy to include short periods of sleep between failed pipe usages. I know that the community generally frowns on such things, but in this case where you may potentially avoid throwing an exception (and failing the CI) I feel it is worth a try. I'll check back with you in a few weeks to see if the extra sleep has improved your mini pipe/process existential crises.

Wishing you all the best,
The Pipe Doctor
There is something rotten in the state of Denmark
Fixing unit tests breaking on da-DK systems,
due to å = aa (last letter in Danish alphabet)
Ats functional tests skip on execution, not discovery
Merge pull request #383 from aspnet/ats627

Ats functional tests skip on execution, not discovery
Recorder destruction... (Removing temporary sequence instrumentation code)

The instrumentation code added this morning provided the results it was designed for. This change removes the code and re-disables the test.
Added code to generate sql for automatically creating/dropping the history table when running migrations.
Fixed a few issues with migrations discovered recently.
Refactored outgoing requests into command pattern