[SPARK-31392][SQL][3.0] Support CalendarInterval to be reflect to Ca…

[yaooqinn]

What changes were proposed in this pull request?

This PR backport #28165 to 3.0.0, previous description shows as:

Since 3.0.0, we make CalendarInterval public for input, it's better for it to be inferred to CalendarIntervalType.
In the PR, we add a rule for CalendarInterval to be mapped to CalendarIntervalType in ScalaRelection, then records(e.g case class, tuples ...) contains interval fields are able to convert to a Dataframe.

Why are the changes needed?

CalendarInterval is public but can not be used as input for Datafame.

scala> import org.apache.spark.unsafe.types.CalendarInterval
import org.apache.spark.unsafe.types.CalendarInterval

scala> Seq((1, new CalendarInterval(1, 2, 3))).toDF("a", "b")
java.lang.UnsupportedOperationException: Schema for type org.apache.spark.unsafe.types.CalendarInterval is not supported
  at org.apache.spark.sql.catalyst.ScalaReflection$.$anonfun$schemaFor$1(ScalaReflection.scala:735)

this should be supported as well as

scala> sql("select interval 2 month 1 day a")
res2: org.apache.spark.sql.DataFrame = [a: interval]

Does this PR introduce any user-facing change?

Yes, records(e.g case class, tuples ...) contains interval fields are able to convert to a Dataframe

How was this patch tested?

add uts

[SparkQA]

Test build #121170 has finished for PR 28198 at commit 10f1e35.

• This patch fails due to an unknown error code, -9.
• This patch merges cleanly.
• This patch adds no public classes.

[yaooqinn]

retest this please

[SparkQA]

Test build #121178 has finished for PR 28198 at commit 10f1e35.

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

[yaooqinn]

cc @dongjoon-hyun @cloud-fan @HyukjinKwon, the backport PR is ready to review thanks

[cloud-fan]

thanks, merging to 3.0!