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
act(() => ReactDOM.render(<Component />, containerA));
    expect(store.supportsProfiling).toBe(true);
    act(() => ReactDOM.render(<Component />, containerB));
    act(() => ReactDOM.unmountComponentAtNode(containerA));
    expect(store.supportsProfiling).toBe(true);
    act(() => ReactDOM.unmountComponentAtNode(containerB));
    expect(store.supportsProfiling).toBe(false);
  });
  it('should properly serialize non-string key values', () => {
    const Child = () => null;
    
    
    const fauxElement = Object.assign({}, <Child />, {key: 123});
    act(() => ReactDOM.render([fauxElement], document.createElement('div')));
    expect(store).toMatchSnapshot('1: mount');
  });
  it('should show the right display names for special component types', async done => {
    async function fakeImport(result) {
      return {default: result};
    }
    const MyComponent = (props, ref) => null;
    const FowardRefComponent = React.forwardRef(MyComponent);
    const MyComponent2 = (props, ref) => null;
    const FowardRefComponentWithAnonymousFunction = React.forwardRef(() => (
      <MyComponent2 />
    ));
    const MyComponent3 = (props, ref) => null;
    const FowardRefComponentWithCustomDisplayName = React.forwardRef(
      MyComponent3,
    );