Generic Extractor date function fix

We have discovered a bug in the Generic extractor, offsetting the string generated by user function `date` by two hours to the "Europe/Prague" timezone.

This error has been fixed and the fix will be deployed on wednesday April 14th. If your extractor uses a date function with `previousStart` time, it might cause a two hour overlap in results of some queries, in case it has been used to set a "since" date for some extraction.

The affected configuration would contain an object such as the following:

{ "start_date": { "function": "date", "args": [ "Y-m-d+H: i", { "time": "previousStart" } ] } }

We apologize for the inconvenience.