[Windowing] Rewrite window function implementation to use real SQLite windows

[ohaibbq]

This drastically improves the performance of complex queries that use window functions by no longer requiring duplicate subqueries and delegating sorting / partitioning to SQLite directly.

For one of our ingest views, the compiled query goes from ~217,000 characters with 272 SELECT statements down to ~117,000 characters with 78 SELECT statements.

The numbering functions such as RANK(), DENSE_RANK(), CUME_DIST() implementations are nearly identical to both SQLite's and Postgres' internal implementation.

SQLite window functions are implemented using the following interface:

Callback	Description
xStep	It is invoked to add a row to the current window. The function arguments, if any, corresponding to the row being added are passed to the implementation of xStep.
xFinal	It is invoked to return the current value of the aggregate (determined by the contents of the current window), and to free any resources allocated by earlier calls to xStep.
xValue	This method is only required for window aggregate functions. The presence of this method is what distinguishes a window aggregate function from a legacy aggregate function. This method is invoked to return the current value of the aggregate. Unlike xFinal, the implementation should not delete any context.
xInverse	This method is only required for window aggregate functions, not legacy aggregate function implementations. It is invoked to remove the oldest presently aggregated result of xStep from the current window. The function arguments, if any, are those passed to xStep for the row being removed.

Closes Recidiviz/recidiviz-data#20742
Closes Recidiviz/recidiviz-data#20739
Closes Recidiviz/recidiviz-data#20740
Closes Recidiviz/recidiviz-data#20751
Closes Recidiviz/recidiviz-data#20773
Closes Recidiviz/recidiviz-data#20754
Closes Recidiviz/recidiviz-data#27338

[ageiduschek]

✨ 🐎 ✨