Removed order implementation for days_ms / Interval(DayTime)

[jorgecarleitao]

The days_ms type cannot be ordered as there is a number of ms m over which (1,m) > (2,0), and thus ordering by days and then by milliseconds is not a valid order. In general such intervals have no order relation.

Thanks a lot to @emkornfield for pointing this here.

All operations relying on order are no longer supported for the logical type Interval(DayTime) (ord, comparison, sort).

[codecov]

Codecov Report

Merging #285 (6645a02) into main (86edfd6) will increase coverage by 0.53%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #285      +/-   ##
==========================================
+ Coverage   77.33%   77.86%   +0.53%     
==========================================
  Files         254      255       +1     
  Lines       20694    21235     +541     
==========================================
+ Hits        16003    16535     +532     
- Misses       4691     4700       +9     

Impacted Files	Coverage Δ
src/array/ord.rs	77.85% <ø> (+0.51%)	⬆️
src/compute/comparison/mod.rs	93.61% <ø> (+2.89%)	⬆️
src/compute/sort/mod.rs	54.00% <ø> (+0.45%)	⬆️
src/types/mod.rs	56.52% <ø> (+4.52%)	⬆️
src/buffer/immutable.rs	97.12% <0.00%> (-0.14%)	⬇️
src/bitmap/utils/mod.rs	100.00% <0.00%> (ø)
src/bitmap/utils/fmt.rs	96.87% <0.00%> (ø)
src/bitmap/mutable.rs	93.33% <0.00%> (+1.16%)	⬆️
src/buffer/mutable.rs	92.93% <0.00%> (+1.17%)	⬆️
src/io/csv/write/mod.rs	88.88% <0.00%> (+1.38%)	⬆️
... and 1 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 86edfd6...6645a02. Read the comment docs.

[emkornfield]

I think we landed on officially day milliseconds being unorderable. There was a comment in the java code at some point that MS component was meant to be less than a day (but I don't think it is enforced any place)