[maven-release-plugin] prepare release 1.14.35
[maven-release-plugin] prepare for next development iteration
Extract EventTapWriter.EventFlow into its own class

EventFlow is no longer an inner class of EventTapWriter but is now its
own independent class: EventTapFlow.

EventTapWriter was also furnished with unit tests.

The licence was updated for all files.
Refactor the interaction between EventTapWriter and BatchProcessor

- Create a BatchProcessorFactory to generate new BatchProcessor objects
- Move logic for cloning batches to multiple taps into the new
  BatchCloner class.
- Create BatchProcessor objects based on need, to avoid queuing up
  events that have no associated tap.
Refactor the interface between EventTapWriter and EventTapFlow

- Create EventTapFlow objects using Guice.
- Decouple the BatchProcessor from the counters.
- Improve testability of EventTapWriter.
Support EventTapFlow with QoS requirements.

Each flow now has its own BatchProcessor (queue and thread) to further
reduce interference between taps of the same type. The EventTapWriter
will also respond to "qos" property of a tap by creating a special QoS
tap (which, for now, is just a normal EventTapFlow object).
[maven-release-plugin] prepare release 1.14.36
[maven-release-plugin] prepare for next development iteration
Support QoS functionality in HttpEventTapFlow

- Send QoS headers to a destination, regardless of QoS status for a
  flow.
- In response to non client-side failures, try other destinations in a
  flow before giving up.
- In response to non client-side failures on a QoS flow, retry sending
  the events after a fixed delay.
Update licence to 2013
[maven-release-plugin] prepare release 1.14.37
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release 1.14.38
[maven-release-plugin] prepare for next development iteration