CDK-604: Added commands to generate logging and Flume configs

* The Flume configuration defaults to an AvroSource listening on 0.0.0.0:41415
* The Flume configuration defaults to a file channel
* The log4j configuration defaults to writing to port 41415, but requires the hostname
* The log4j configuration requires a package or class name to log to Flume, or a
  switch of --log-all to configure the rootLogger.
* Besides the unit tests, I ran some manual tests on a cluster by completing the
  logging example, but using the tool derived configs rather than the ones that
  shipped with the example.
Makes sense, but I think we should change the name to reflect where the events are going. We expect users to switch out the source more often than the sink (hopefully) so naming it after the sink would be less to edit when making the change. And basing the name on the sink name rather than choosing a default that corresponds to the example will make it so that users don't have to worry about this setting most of the time.