[FEATURE] Integrate query results with grafer

[adamocarolli]

What? Highlight query results on Grafer layers.

Why? Users can now see their queries highlighted in the larger graph for context.

How?

• BGraph query results require a mapping to Grafer's data. So we load Grafer's data in the bio view and store the mappings we need as properties in that view
• When a user submits a lex/facets search the event is caught by a query change event in the bio view which then takes the bgraph results and builds grafer layers using the stored grafer data (Highlight layers.)
• The layers are sent to the Grafer component for rendering via an event hub.

Testing? Run queries and see if the highlights are as expected.

Anything Else?

• I pre-emptively added edge highlighting. However, we have no UI inputs for specifying a query that'd have edge results.
• I noticed combination queries are not working. I think this is happening upstream of this change.

[RosaRomeroGomez]

Two comments/thoughts:

• I think we want to have Grafer base layer highlighted or visible by default. The idea is the user opens this view to get an overview of the whole COVID-19 knowledge graph. If we have it faded it out by default, it doesn't provide much context to the user. In summary, I think in the default state (when there are no query results), everything should be visible. Then, when we start applying filters and facets, we start applying the idea of background/foreground layers.
• I've also noticed (and this is probably out of the scope of this PR), that we currently can run queries while Grafer is loading. This currently throws some errors in the console. We might want to disable the search until Grafer is loaded?

[adamocarolli]

Two comments/thoughts:

• I think we want to have Grafer base layer highlighted or visible by default. The idea is the user opens this view to get an overview of the whole COVID-19 knowledge graph. If we have it faded it out by default, it doesn't provide much context to the user. In summary, I think in the default state (when there are no query results), everything should be visible. Then, when we start applying filters and facets, we start applying the idea of background/foreground layers.
• I've also noticed (and this is probably out of the scope of this PR), that we currently can run queries while Grafer is loading. This currently throws some errors in the console. We might want to disable the search until Grafer is loaded?

@RosaRomeroGomez

1. Good idea! Done in this PR: https://github.com/uncharted-aske/HMI/pull/183
2. Fixed in this commit: https://github.com/uncharted-aske/HMI/pull/178/commits/d2bb22d64d317394a41ec5850d13b344dd884e63