Improve sqlite logging unit tests

By using a consistent timestamp. That avoids rare chances of sqlite
output from rounding the current time into such a form that happens
to bypass the timestamp canonifier script (whenever it happened to
land on a whole or tenth second).

CHANGES

@@ -1,4 +1,8 @@
 
+2.6-379 | 2019-06-06 11:56:58 -0700
+
+  * Improve sqlite logging unit tests (Jon Siwek, Corelight)
+
 2.6-378 | 2019-06-05 16:23:04 -0700
 
   * Rename BRO_DEPRECATED macro to ZEEK_DEPRECATED (Jon Siwek, Corelight)

VERSION

@@ -1 +1 @@
-2.6-378
+2.6-379

testing/btest/scripts/base/frameworks/logging/sqlite/error.zeek

@@ -93,7 +93,7 @@ event zeek_init()
 		$sn=10.0.0.1/24,
 		$a=1.2.3.4,
 		$d=3.14,
-		$t=network_time(),
+		$t=double_to_time(1559847346.10295),
 		$iv=100secs,
 		$s="hurz",
 		$sc=set(1,2,3,4),

testing/btest/scripts/base/frameworks/logging/sqlite/simultaneous-writes.zeek

@@ -73,7 +73,7 @@ event zeek_init()
 		$sn=10.0.0.1/24,
 		$a=1.2.3.4,
 		$d=3.14,
-		$t=network_time(),
+		$t=double_to_time(1559847346.10295),
 		$iv=100secs,
 		$s="hurz",
 		$sc=set(1,2,3,4),

testing/btest/scripts/base/frameworks/logging/sqlite/types.zeek

@@ -65,7 +65,7 @@ event zeek_init()
 		$sn=10.0.0.1/24,
 		$a=1.2.3.4,
 		$d=3.14,
-		$t=network_time(),
+		$t=double_to_time(1559847346.10295),
 		$iv=100secs,
 		$s="hurz",
 		$sc=set(1,2,3,4),