Centralise logging

Summary:
Centralise connectivity logging into a single place. By having all logs go through a single interface, then it becomes trivial to manipulate them as needed.

In this change, this is not done.

In subsequent diffs, logs will be dispatched via an event and will be visualised in the Connectivity Hub.

Reviewed By: passy

Differential Revision: D47185054

fbshipit-source-id: fb5eab98895be0c8f61fb9a77d3e66d6a8dbcb27

desktop/flipper-ui-core/src/chrome/ConnectivityHub.tsx

@@ -10,6 +10,6 @@
 import {Layout} from '../ui';
 import React from 'react';
 
-export function ConnectionTroubleshootTools() {
+export function ConnectivityHub() {
   return <Layout.Container grow>Connection Troubleshoot</Layout.Container>;
 }

desktop/flipper-ui-core/src/sandy-chrome/SandyApp.tsx

@@ -44,7 +44,7 @@ import {isFBEmployee} from '../utils/fbEmployee';
 import {notification} from 'antd';
 import isProduction from '../utils/isProduction';
 import {getRenderHostInstance} from 'flipper-frontend-core';
-import {ConnectionTroubleshootTools} from '../chrome/ConnectionTroubleshootTools';
+import {ConnectivityHub} from '../chrome/ConnectivityHub';
 
 export type ToplevelNavItem =
   | 'appinspect'
@@ -91,7 +91,7 @@ export function SandyApp() {
           dispatch(setStaticView(FlipperDevTools));
           break;
         case 'connectivity':
-          dispatch(setStaticView(ConnectionTroubleshootTools));
+          dispatch(setStaticView(ConnectivityHub));
           break;
         default:
       }