Append and show errors which are caused due to jni/native crashes

Summary:
Before this diff, the crash reporteer plugin for android just used to show messages which were error and had tag as "AndroidRuntime". This diff fixes this and instead accepts multiple different tags which might be related to crashes.

The issue with triggering the notification for all kind of messages would be that, the user might get many. For the jni errors, the stack trace of it are shown as multiple entry instead of one entry in logcat. So to combine all the stack trace into one callstack message, this diff adds a timer of 10ms and combines the messages which occur in that timespan and then trigger the notification.

Reviewed By: danielbuechele

Differential Revision: D13772505

fbshipit-source-id: fec6f5a7f9f46948c9f9dc5b2a7b92690913c8aa

src/index.js

@@ -26,7 +26,12 @@ export type {Store} from './reducers/index.js';
 export {
   default as SidebarExtensions,
 } from './fb-stubs/LayoutInspectorSidebarExtensions.js';
-export {DeviceLogListener, DeviceLogEntry} from './devices/BaseDevice.js';
+export {
+  DeviceLogListener,
+  DeviceLogEntry,
+  LogLevel,
+} from './devices/BaseDevice.js';
+export {shouldParseAndroidLog} from './fb-stubs/crashReporterUtility.js';
 export {createTablePlugin} from './createTablePlugin.js';
 export {default as DetailSidebar} from './chrome/DetailSidebar.js';