Here are the different ways we record events in the context of ntp suggestions:

- UMA recorded directly from Java: NewTabPageUMA, maybe other things
- UMA recorded inderectily through the content suggestions metrics backend: SnippetsBridge
- Events notified to the scheduler: SnippetsBridge. We just send usage signals to the scheduler so that is can adjust the fetch frequency.
- Other?

A first issue with the way we do that currently is that the general metrics recording should not be tied to a bridge instance. The metrics recording itself is done through plain functions.
Event notifications themselves also doesn't need it as it is all related to the single content suggestions service that is accessible through the profile anyway.

That would leave the SnippetsBridge with functions related to being a suggestions source and more 2 way communication between java and c++.

The second issue is how some general suggestions metrics should not care about being in the NTP or not, so move out of NewTabPageUMA.