test: add platform checks for RANGE type

[nrainer-materialize]

Motivation

Add platform checks for RANGE types. This fixes #17815.

Status

This is a draft (see comments).

[philip-stoev]

[2023-04-11T08:57:25Z] rows didn't match; sleeping to see if dataflow catches up 50ms 75ms 113ms 169ms 253ms 380ms 570ms 854ms 1s 2s 3s 4s 6s 10s 15s 22s 33s 49s 74s 78s
--
  | [2023-04-11T08:57:26Z] 40:1: error: non-matching rows: expected:
  | [2023-04-11T08:57:26Z] [["U2", "A", "1000"]]
  | [2023-04-11T08:57:26Z] got:
  | [2023-04-11T08:57:26Z] [["U2", "A", "560"]]
  | [2023-04-11T08:57:26Z] Poor diff:
  | [2023-04-11T08:57:26Z] - U2 A 1000
  | [2023-04-11T08:57:26Z] + U2 A 560
  | [2023-04-11T08:57:26Z]
  | [2023-04-11T08:57:26Z]      \|
  | [2023-04-11T08:57:26Z]   39 \|
  | [2023-04-11T08:57:26Z]   40 \| > SELECT * FROM "7";
  | [2023-04-11T08:57:26Z]      \| ^

This is an unrelated regression that has been fixed on main. Consider rebasing so that you are not bothered by sporadic failures as you develop.

[philip-stoev]

This is all good and in fact quite readable, so please do leave it as it is, but for the record the same can be achieved with format strings:

return [ Testdrive(f" range_view{i} ") for i in [1,2]]

or something along those ines.

[philip-stoev]

Thank you! Looks good and does what was needed from this test!

[nrainer-materialize]

#18817 has been merged, rebased on main.