[Flink] Support comparing UT (Unit Test) results with Flink.

### Description

Currently, we verify UT results by providing expected outcomes. This approach lacks flexibility for two main reasons:
- manually specifying expected results is cumbersome, and
- as Flink evolves, its execution results may change. In such cases, we must manually update the previously provided expected results to maintain consistency.

We aim to achieve an effect similar to Spark's, where UTs are executed once in both Flink and Gluten, and their results are compared.

### Gluten version

None

No files, tests, or entry points are named. Start by locating the existing unit-test result verification and the Spark-style comparison approach, then determine how Flink and Gluten should execute the same tests. Done means their results are compared without manually maintaining expected outcomes as Flink changes.

Written by the indexing model from the issue text.