make the logging wrapper class output to core.console

This makes our logging class, `Logging.Log`, output to Freedom's `core.console` rather than directly to the browser's `console`.

The advantage of this is that `core.console` is smart enough to route messages to the terminal on Firefox, if you're using `cfx run`.

This does *not* implement a Freedom "custom logger" which would serve as a central collection point (and filtering, retrieval, etc. etc.). We should consider that in the future but I don't think there's a compelling reason to do it right now (basically, much of the code in `Logger.Log` would move to a custom logger).

`core.console` does a little formatting of its own so I had to tweak `Logging.Log`'s output a little. It now looks like this in Chrome:

![image](https://cloud.githubusercontent.com/assets/5142116/4903718/c79cc990-6442-11e4-9dc8-4319d4a298db.png)
Why did you remove this?  Is it just because Logging.Log is overkill when running in a webpage?  I wonder if it would be worth keeping, because otherwise uproxy-lib wouldn't contain a sample that uses Logging.Log.