Update date-fns to 2.9.0

[megastef]

Migrating from date-fns@2.0-alpha6 to date-fns@2.9.0. Including changes for backward compatibility.

• update existing patterns to new date-fns format strings
• auto-fix for old dateFormat strings. If such a fix is applied, the parser generates a 1-time warning while loading patterns. The auto-fix converts YY -> yy, DD -> dd, Z -> X and sets 'iso' for ISO date patterns, which must be handled by a separate 'parseISO' function. See: https://github.com/date-fns/date-fns/issues/1643

Parser config: You use a deprecated dateFormat in sematext_agent_golang 'YY-MM-ddTHH:mm:ss'' was converted to 'iso' - check your patterns.yml file
Parser config: You use a deprecated dateFormat in sematext_agent_golang 'YY-MM-ddTHH:mm:ss'' was converted to 'iso' - check your patterns.yml file
Parser config: You use a deprecated dateFormat in mongodb 'yyyy-MM-ddTHH:mm:ss.SSSZ'' was converted to 'iso' - check your patterns.yml file
Parser config: You use a deprecated dateFormat in nexus 'yyyy-MM-dd HH:mm:ss,SSSZ'' was converted to 'yyyy-MM-dd HH:mm:ss,SSSX' - check your patterns.yml file

When debug is enabled via DEBUG=true or CLI arg -v or dev=bug:true in patterns.wml, users get for each parsed line such a message:

Error parsing date, wrong date format: 03/Apr/2016:06:25:38 +0000 DD/MMM/yyyy:HH:mm:ss Z
See https://date-fns.org/v2.9.0/docs/parse for more information.

• a fix for the docker input-plugin to take always docker timestamps. On the Docker platform, we are in a good situation that timestamps are available. And nobody needs to rely on date parsing.