ST_CROSSES always returns 0 for geometries of different dimensions

Version 11.4.11 introduced a regression in ST_Crosses:

SELECT ST_Crosses(ST_GeomFromText('MULTIPOINT(1 3, 2 2, 3 2)'),

                  ST_GeomFromText('LINESTRING(0 3, 1 1, 2 2, 2 0)'));

-- expected: 1

-- actual  : 0

SELECT ST_Crosses(ST_GeomFromText('MULTIPOINT(1 1, 1 3, 2 3)'),

                  ST_GeomFromText('POLYGON((0 0, 0 3, 2 0, 0 0))'));

-- expected: 1

-- actual  : 0

SELECT ST_Crosses(ST_GeomFromText('LINESTRING(0 1, 3 2, 4 1)'),

                  ST_GeomFromText('POLYGON((1 0, 1 2, 2 3, 2 1, 1 0))'));

-- expected: 1

-- actual  : 0

All three queries return 1 on MariaDB 11.4.10 and earlier, and on MySQL 8.4.7 and 9.6.0. PostGIS (3.5.2 and 3.6.4) and GEOS (3.10.2 and 3.14.1) also report these geometries as crossing.

Starting with 11.4.11, MariaDB returns 0 for every ST_CROSSES call where the two geometries have different dimensions.

ST_Overlaps requires geometries of the same dimension, but ST_Crosses is defined precisely for geometries of different dimensions.

This regression seems to have been introduced by MDEV-36058.