Building on top of #360

We could probably improve the search UX in a couple of ways:

* Visually indicate when the "match" is because of a HOC name, e.g.
<img width="161" alt="Screen Shot 2019-08-03 at 1 54 21 PM" src="https://user-images.githubusercontent.com/29597/62416804-36f32f00-b5f6-11e9-9150-e32f652c7f98.png">

* Match built-in HOC types (e.g. searching "me" should match `React.memo` HOCs, searching "f" should match `React.forwardRef`, etc.)

---
Originally reported via https://github.com/bvaughn/react-devtools-experimental/issues/365
FowardRefComponentWithCustomDisplayName.displayName = 'Custom';
    const MyComponent4 = (props, ref) => null;
    const MemoComponent = React.memo(MyComponent4);
    const MemoForwardRefComponent = React.memo(FowardRefComponent);
    const MyComponent5 = (props, ref) => null;
    const LazyComponent = React.lazy(() => fakeImport(MyComponent5));
    const App = () => (
      <React.Fragment>
        <MyComponent />
        <FowardRefComponent />
        <FowardRefComponentWithAnonymousFunction />
        <FowardRefComponentWithCustomDisplayName />
        <MemoComponent />
        <MemoForwardRefComponent />
        <React.Suspense fallback="Loading...">
          <LazyComponent />
        </React.Suspense>
      </React.Fragment>
    );
    const container = document.createElement('div');
    
    act(() => ReactDOM.render(<App />, container));
    await Promise.resolve();
    
    act(() => ReactDOM.render(<App />, container));
    expect(store).toMatchSnapshot();
    done();
  });
});