[FLINK-33722] Fix events ordering in MATCH_RECOGNIZE in batch mode

[grzegorz8]

What is the purpose of the change

Currently, MATCH_RECOGNIZE completely ignores the ORDER BY clause in batch mode: the events are processed in the order they come which makes no sense. This pull request adds proper events ordering in Pattern Recognition for batch.

Brief change log

• Fix events ordering in MATCH_RECOGNIZE in batch mode

Verifying this change

This change added tests and can be verified with org.apache.flink.table.planner.runtime.batch.sql.MatchRecognizeITCase. Existing tests have been modified. A few new tests have been added - they are simiar to the ones in org.apache.flink.table.planner.runtime.stream.sql.MatchRecognizeITCase.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• 0fee492a076714f17aa8548b94cb55c4f52fc446 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build