Feature/gh 1517 single port

[wlycdgr]

Implements dynamic updating of the extension panel UI including the Summary and Detailed views. This includes dynamic updating of the various tracker counts as the page loads, dynamic insertion of trackers into the blocking list as they are found, and dynamic redrawing of the donut graph.

Streamlines all UI data transfer between the panel (including its Panel, Summary, Blocking, Settings, and Rewards components) and the background to use a single port managed by PanelData on the backend and passed through using the Context API on the React frontend, obviating all such transfer through message passing.

Factors out Cliqz antitracking and adblocking modules data retrieval into a utility file that both BrowserButton and PanelData can use, reducing duplication across BrowserButton and PanelData & the GET_CLIQZ_MODULE_DATA reducer on the front end.

Refactors FoundBugs to more efficiently handle the now potentially much larger volume of requests for bug info, primarily by storing foundApps data alongside foundBugs data so it does not need to be repeatedly recalculated.

Refactors and simplifies PanelData.

• Have you followed the guidelines in CONTRIBUTING.md?
• [N/A] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you added an explanation of what your changes do?
• Does your submission pass tests?
• Did you lint your code prior to submission?

[jsignanini]

@wlycdgr let's rework it so that it follows this sequence:

1. panel is opened
2. get all panelData at that point in time and send to panel to display
3. concurrently, trigger a call to getUserSettings(), once it returns, if the panel is still open, stream the new settings data to panel to display (through the same method as point 2)
4. from now on, the only data streamed live to the panel is non-persistent data: tabInfo, apps, trackers, page load times, etc. Basically data that only lives for the "tab" session

[wlycdgr]

@jsignanini I've rewritten and reorganized PanelData to follow the sequence you outlined.

[jsignanini]

@wlycdgr panel shows blank (check console.log for errors) when opening on chrome://* or chrome-extension://* pages right after install.

[wlycdgr]

@wlycdgr panel shows blank (check console.log for errors) when opening on chrome://* or chrome-extension://* pages right after install.

@jsignanini fixed