Feature/metrics-timeresolution-support

Test cases for having Time series table with resolution for a minute and bug fixes to support that.

Time series table previously just writes the new data as we only tested resolution with a second, with minute aggregation , we would want to add to the previous timestamp if an entry exists and the metric type is counter, so added increment support in the time series table.

https://issues.cask.co/browse/CDAP-625
I understand what the change is doing.  The point I am making is that this will change what used to be a put into an increment, and I am wondering whether or not we have made sure that anybody who is calling this code was not relying on the previous put behavior.