Bug fix for pmloglib

:Release Notes:
Fixed bug the value string length is over 1024 bytes when
using PMLOGKS().

:Detailed Notes:
It is occurred segmentation fault when the value parameter is
inputted over 1024 bytes when using PMLOGKS().
Modified logic for strstr().
PmLogDaemon can handle log message up to 1024 bytes as well.
80~100 bytes timestamp, monotictime, facility, level,
process name, pid:tid, ContextName and MsgID compose
first section and rest of bytes can be used for json and
free text message.
As as result, if json and free text message section exceed about
900 bytes PmLogLib will truncate the string.
This process can truncated middle of json string.
Then, the truncated json string become wrong format.
So, two error message will be presented in /var/log/messages
below.

MSG_TRUNCATED {"CONTEXT":"PMLOGLIB_PERF","MSGID":"TEST_MSGID",
"CAUSE":"Log message exceeded 1024 bytes"}
INVALID_JSON {"CONTEXT":"PMLOGLIB_PERF","MSGID":"TEST_MSGID",
"CAUSE":"The json string has truncated",
"TRUNCATED":{"key":"+KYpU9B3HtyH5P7vk4jkUvhe95JcpCiESe8hyen1pjbzb
1lLiNXfAbp1znyItLuBa4h5s1l+Ey+iJdCd3l4iO+KYpU9B3HtyH5P7vk4jkUvhe9
5JcpCiESe8hyen1pjbzb1lLiNXfAbp1znyItLuBa4h5s1l+Ey+iJdCd3l4iO+KYpU
9B3HtyH5P7vk4jkUvhe95JcpCiESe8hyen1pjbzb1lLiNXfAbp1znyItLuBa4h5s1
l+Ey+iJ ..."}}

:Testing Performed:
Compiled locally and tested on emulator and devices.
Verified in the log file, error text displayed in
/var/log/messages properly.

:QA Notes:

:Issues Addressed:
[GF-35130] SunSpider benchmarks cause PmLogLib crash in WAM2

Open-webOS-DCO-1.0-Signed-off-by: Hongjeon Ha <hj.ha@lge.com>

Change-Id: I4b7c933a3e786f952045cfd4229389337c851a1a
Reviewed-on: https://g2g.palm.com/3284
Reviewed-by: Build Verification
Reviewed-by: Hongjeon Ha <hj.ha@lge.com>
Tested-by: Hongjeon Ha <hj.ha@lge.com>
Reviewed-by: Keith Derrick <keith.derrick@lge.com>