Add support for Container Runtime Interface (CRI) log format

[sydp]

Describe the problem:

Kubernetes uses the CRI log format for container stdout/stderr log streams.

Additional context

Per https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kuberuntime/logs/logs.go#L125, CRI log format example:

2016-10-06T00:17:09.669794202Z stdout P log content 1
2016-10-06T00:17:09.669794203Z stderr F log content 2

where "log content 1", "log content 2" can be another log format e.g. apache access log.

Archived design proposal: https://github.com/kubernetes/design-proposals-archive/blob/main/node/kubelet-cri-logging.md

[sydp]

Was discussing with @roshanmaskey OOB today who expressed an interest to work on this as he has more familiarity with containerd/k8s (container-explorer) .

[sydp]

Datetime strings are formatted with nanosecond precision. These values appear to be based on the Golang time module.

https://github.com/log2timeline/dfdatetime/issues/263