Report system OOM in the log

:Release Notes:
pmklogd catches kernel messages when OOM happens and logs
them in pmloglib format. OOM messages are also routed to
a file for crash report generation.

:Detailed Notes:
Problem:
Right now there is no log statement in system logs when the
system OOM kills a process and bugs should be reported
automatically when system OOMs out.

Solution:
pmklogd catches the kernel messages, looks for OOM information
and routes them to a file, from which crashd and eventually rdxd
creates a crash report for bugreportd. pmklogd also logs the cause
and victim of OOM into /var/log/messages

Future replacement:
This feature should be removed from pmklogd, once there is a
notitication interface implemented in the kernel. Crashd should
then recieve OOM related information via the notification interface
and log system OOM condition in /var/log/messages.

:Testing Performed:
Compiled and tested on the device.
Used memgrabber program to simulate a system OOM. Verified that
logs show OOM cause and victim. Also, rdx crash reports are created
and uploaded to the server.

:QA Notes:

:Issues Addressed:
[GF-45165] pmklogd should catch OOM messages from kernel

Open-webOS-DCO-1.0-Signed-off-by: Gayathri Srinivasan <gayathri.srinivasan@lge.com>

Change-Id: I66ade04d6519b9d624fa445cb4d15416f9a83497
Reviewed-on: https://g2g.palm.com/3821
Reviewed-by: Build Verification
Reviewed-by: Gayathri Srinivasan <gayathri.srinivasan@lge.com>
Tested-by: Gayathri Srinivasan <gayathri.srinivasan@lge.com>
Reviewed-by: Keith Derrick <keith.derrick@lge.com>