logging: init logging early, hand ProxyFetchFactory correct server log

- Prevent logging to stdout/stderr, make sure we log to error.log for
early messages during initialization. Note that nginx is still working
to setup its logging configuration, so these early messages will go
through its defaults. Which means that only warnings or worse will pass
for early logging messages.
- Make sure we init ProxyFetchFactories's NgxMessageHandler to the correct
server{} specific log so it will write to the error_log configured
in the server{} block instead of the global error_log.

Fixes https://github.com/pagespeed/ngx_pagespeed/issues/808
Helps https://github.com/pagespeed/ngx_pagespeed/issues/817
@crowell This code path is already protected by `factory_deleted`, so `factory_init_called` shouldn't make a difference here after the first call. I could go either way on that though.
However, one of the reasons why we need to do this here is because this sequence seems to CHECK fail when there is an explicit cache configuration specified. (I forgot to add a code comment about that):
```C++
NgxRewriteDriverFactory* factory = new NgxRewriteDriverFactory(...);
// This call is *required*
// factory->Init()
delete factory;
```

Is that by design? If it wouldn't do that, we wouldn't have to call `factory->Init()` here during shutdown, and hence drop the `factory_init_called` flag altogether. (Calling `factory->LoggingInit(ngx_cycle->log);` multiple times shouldn't be a problem.)