CXX-265 Configure logging through startup options

A few comments/questions:

-For cleanup of appenders, there's a clearAppenders() function, and this will actually delete the appenders.  Though it seems clear that when you attach the appender you hand ownership of it over to the log domain, users using these options won't see that call, and I wonder if they'd be surprised by this behavior.  Also, since we're not using the appender handles at all, or allowing the user to use them, I wasn't sure how important it was to call clearAppenders() at all.

-Where should configureLoggingOptions() live?  Options.cpp seems like an ok option, but I think there's probably a better fit.  If I add a cleanup function that should probably live in the same place.

-Should there be a way to configure, through options, specific minimum logged severity levels for different logging domains?  If you were doing it manually, you'd be able to set it by component.
Right, good point about the integration tests calling initialize too early.

We have a bit of a confusion about what is a test and what is an example. And we need both, in this case: I'd really like an example that demonstrates to a user how to set up the logging system. We have some of that in clientTest right now.

But we also need a test to make sure that what we put into the options for logging works. And that runs into problems with calling initialize.

Similarly, as an example, having LOG here is a little odd because users of the library can't actually use it. We don't actually want users to *use* our logging system, just to be able to get events from it, presumably to propagate into their own logging system.

Lets punt on this for now and leave this test as is and revisit once we have sorted out some of the other issues.