fix(sql): Fix intermittently failing tests (#2788)

Some of the execution repository tests assert the ordering of
executions retreived from the database, but ULIDs are only
monotonic with millisecond resolution. The fix has been to sleep
for 1ms beteween creating executions, which mostly fixed the tests
but there are still occasional failures where two executions have
the same timestamp bits in their ULID.

To reduce these failures, just wait 5ms between adding executions to
the database.

orca-core-tck/src/main/groovy/com/netflix/spinnaker/orca/pipeline/persistence/ExecutionRepositoryTck.groovy

@@ -158,7 +158,7 @@ abstract class ExecutionRepositoryTck<T extends ExecutionRepository> extends Spe
     when:
     repository.store(runningExecution)
     // our ULID implementation isn't monotonic
-    sleep(1)
+    sleep(5)
     repository.store(succeededExecution)
     def orchestrations = repository.retrieveOrchestrationsForApplication(
       runningExecution.application,

orca-sql/src/test/groovy/com/netflix/spinnaker/orca/sql/pipeline/persistence/SqlExecutionRepositorySpec.groovy

@@ -291,7 +291,7 @@ class SqlExecutionRepositorySpec extends ExecutionRepositoryTck<SqlExecutionRepo
         name = "Orchestration #${i + 1}"
       })
       // our ULID implementation isn't monotonic
-      sleep(1)
+      sleep(5)
     }
 
     when:
@@ -351,7 +351,7 @@ class SqlExecutionRepositorySpec extends ExecutionRepositoryTck<SqlExecutionRepo
         name = "Orchestration #${i + 1}"
       })
       // our ULID implementation isn't monotonic
-      sleep(1)
+      sleep(5)
     }
 
     when:
@@ -384,7 +384,7 @@ class SqlExecutionRepositorySpec extends ExecutionRepositoryTck<SqlExecutionRepo
         name = "Orchestration #${i + 1}"
       })
       // our ULID implementation isn't monotonic
-      sleep(1)
+      sleep(5)
     }
 
     when: