TAJO-904: ORDER BY with a null column miss some data.

Currently Tajo ignores null value when calculates range partition range.  I added a MaxValueNull flag variable in ColumnStats. If ColumnStats's max value is null, ColumnStats's max value is a non-null value and  MaxValueNull flag is true. So Repartitioner calculates range cardinality with non-null value. Finally Repartitioner set null value to last range.
It should be ```DROP TABLE IF EXISTS table 1 PURGE```. Otherwise, it will cause 'no such table error' when a developer executes this test separately.