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
but you do a get on increments, and if it's not null, the difference between the increment value and value passed in will get placed in the gauges table which seems wrong (unless it's guaranteed that keys never overlap between the two tables?).  In any case, the point is that this method is very confusing because it is unrelated things. Can we just split it up.