Fix structure and execution of type tests

[martint]

Do not use inheritance/overriding for code reuse and specialization, as it makes it harder to reason about what's being tested.

Also, annotate the tests directly so that they are picked up by JUnit

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

[hashhar]

how do we plan to deal with evolving tests? e.g. if you add a new test testRange then how do you identify which all test classes it should go into? Similarly how do you ensure there isn't a drift in the test method definition across classes.

[martint]

Each type needs tests according to its semantics. If you add new behavior to a type that affects how getRange() works, the corresponding tests for that type need to be adjusted. That's no different than how we implement tests for timestamp, timestamp w/ tz, time, time w/ tz, etc. in io.trino.operator.scalar.timestamp.TestTimestamp, io.trino.operator.scalar.timestamp.TestTime, and friends.