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
it doesn't  copy increments table to gauges table. if the record we iterate (records received in 1 second interval), if we have already seen and stored in the table, and if its an increment then we read the old value and add it up, then finally store it in increments table.  

ultimately we do a put into a map, and we decide based on the record type, if we are going to add this to increments map or gauges map 

```put((type == MetricType.COUNTER) ? incrementsTable : gaugesTable, rowKey, column, Bytes.toBytes(newValue));```

the assumption we make is we don't mix gauge and counter for a metric. ie if the metric is process.events, it would consistently use increment and not call gauge on that metric type.