STORM-495: KafkaSpout retries with exponential backoff

This is an implementation of the improvement request STORM-495.

The KafkaSpout keeps track of failed messages through multiple retries, and delays their resubmission to the topology with an exponentially increasing delay time.  The spout does not terminate the retry cycle (it is my conviction that it should not do so, because it cannot report context about the failure that happened to abort the reqeust), it only handles delaying the retries.  A bolt in the topology is still expected to eventually call ack() instead of fail() to stop the cycle.
This is the only place where retryRecords.remove() is called, so if a message keeps failing it will never be removed from this Map in other words we seem to be leaking instances here.