[SPARK-31912][SQL][TESTS] Normalize all binary comparison expressions

[wangyum]

What changes were proposed in this pull request?

This pr normalize all binary comparison expressions when comparing plans.

Why are the changes needed?

Improve test framework, otherwise this test will fail:

  test("SPARK-31912 Normalize all binary comparison expressions") {
    val original = testRelation
      .where('a === 'b && Literal(13) >= 'b).as("x")
    val optimized = testRelation
      .where(IsNotNull('a) && IsNotNull('b) && 'a === 'b && 'b <= 13 && 'a <= 13).as("x")
    comparePlans(Optimize.execute(original.analyze), optimized.analyze)
  }

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Manual test.

[SparkQA]

Test build #123557 has finished for PR 28734 at commit dbc4614.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[cloud-fan]

do you have a use case for it? why do we intentionally switch the operand order?

[wangyum]

I encountered this issue when inferring from inequality attributes before, Its order may change:

spark/sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/InferFiltersFromConstraintsSuite.scala

Lines 402 to 407 in bfa6039

	test("Constraints inferred from inequality attributes: case2") {
	val original = testRelation.where('a < 'b && 'b < 'c && 'c < 5)
	val optimized = testRelation.where(IsNotNull('a) && IsNotNull('b) && IsNotNull('c)
	&& 'a < 'b && 'b < 'c && 'c > 'a && 'a < 5 && 'b < 5 && 'c < 5)
	comparePlans(Optimize.execute(original.analyze), optimized.analyze)
	}

[cloud-fan]

ok makes sense, LGTM. It's for a new feature, so merging to master should be good enough?

[wangyum]

Merged to master.