Add Settings.renderImplicitWindowRange handling different default window RANGE clause defaults

[lukaseder]

In Teradata, the default RANGE clause (or rather, ROWS clause, because RANGE isn't supported) is always ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING, irrespective of the presence of an ORDER BY clause:

drop table t;
create table t (a int);
insert into t values (1);
insert into t values (2);
insert into t values (3);
insert into t values (4);

select 
  sum(a) over (order by a),
  sum(a) over (order by a rows between unbounded preceding and current row)
from t

The result being:

|Group Sum(a)|Cumulative Sum(a)|
|------------|-----------------|
|10          |1                |
|10          |3                |
|10          |6                |
|10          |10               |

So, ORDER BY has no effect on aggregate window functions, if not accompanied by a ROWS clause. We might want to offer tooling to standardise this behaviour.

• OFF Don't generate anything extra (default, current behaviour, opt out option for this improvement)
• RANGE_UNBOUNDED_PRECEDING Emulate standard behaviour
• RANGE_ALL Emulate Teradata behaviour
• ROWS_UNBOUNDED_PRECEDING Emulate standard behaviour (but use ROWS instead of RANGE)
• ROWS_ALL Emulate Teradata behaviour (but use ROWS instead of RANGE)

The five flags will allow for all desirable configurations:

• "Emulate standard behaviour" is great when an application is written with jOOQ, and now Teradata support is added to the application
• "Emulate Teradata behaviour" is useful when using the parser to migrate from Teradata to something else.

[lukaseder]

Commit will be included with this issue here: #11850