[IOTDB-1531] Check tsfile creation time when recovering

[HeimingZ]

Check tsfile's time when recovering, make sure all tsfile time are less than System.currentTimeMillis(). If the tsfile's time is larger than System.currentTimeMillis(), the recover of corresponding virtual storage group will fail, users cannot read/write this virtual storage group until the time of the tsfile is correct.

Before fixing time：

After fixing time：

[coveralls]

Coverage decreased (-0.007%) to 68.217% when pulling bccd936 on HeimingZ:IOTDB-1531(check_tsfile_time_when_recovering) into 0b2d0af on apache:master.

[wangchao316]

I have a little question. why all tsfile time are less than System.currentTimeMillis()?
if tsfile time are better than System.currentTimeMillis(), Does iotdb-server used?
The time of real data may change due to a fault in the collection device (data is later than the current time). In this case, the entire cluster cannot be used.

[HeimingZ]

I have a little question. why all tsfile time are less than System.currentTimeMillis()?
if tsfile time are better than System.currentTimeMillis(), Does iotdb-server used?
The time of real data may change due to a fault in the collection device (data is later than the current time). In this case, the entire cluster cannot be used.

This pr aims to make sure server time zone is correct and all tsfiles' created time is less than system current time. It only compares the created time of tsfile, which is determined by the server, so data from devices won't affect the use of iotdb.