dont log plugin message queue when plugin processing takes too long

Summary:
While profiling the bloks debugger i noticed that in the heap snapshot the largest strings were these log messages. this is because we log the entire message queue which can be enormous.

this creates a negative feedback loop in that the giant string adds additional memory pressure.

Reviewed By: passy

Differential Revision: D64105989

fbshipit-source-id: 495913ae886196825a1c949b6b3980f56c241cee

desktop/flipper-ui/src/utils/pluginStats.tsx

@@ -126,8 +126,8 @@ export function addBackgroundStat(
   stat.maxTime = Math.max(stat.maxTime, cpuTime);
   if (cpuTime > MAX_BACKGROUND_TASK_TIME) {
     console.warn(
-      `Plugin ${plugin} took too much time while doing background: ${cpuTime}ms. Handling background messages should take less than ${MAX_BACKGROUND_TASK_TIME}ms.`,
-      messages,
+      `Plugin ${plugin} took too much time while doing background: ${cpuTime}ms. Handling background messages should take less than ${MAX_BACKGROUND_TASK_TIME}ms. message queue length`,
+      messages.length,
     );
   }
 }