implemented reporting of profiler data via scribe

@Wikia/platform-team pls review
Hi, I totally agree your point and I share it. What makes hard for me to follow it is that the current architecture breaks it by merging at least two responsibilities: collecting data and reporting/sending them. 

On the other hand collecting data (in case of Mediawiki profiler) can be started before all dependencies for reporting it are loaded (and should to better visualize how the server time is used).

I tried to reuse ProfilerSimpleUDP class to handle reporting via Scribe because it was the only one that is designed to send data to remote destination. At the same time the bootstrapping flow first initializes the Profiler subclass and the global variables are loaded later so I wouldn't know what subclass to instantiate ProfilerSimpleUDP or ProfilerSimpleScribe.

I think that it might be hard to correct the issues you mentioned without a major refactor that I wanted to avoid. Any opinion how to solve the issue at this point?