[SPARK-38163][SQL] Preserve the error class of SparkThrowable while constructing of function builder

[MaxGekk]

What changes were proposed in this pull request?

In the PR, I propose to propagate SparkThrowable to user space AS IS in constructing of function builder. This allows to preserve the error class, for instance.

Why are the changes needed?

This fixes the issues portrayed by the example below:

scala> try { sql("select format_string('%0$s', 'Hello')") } catch { case e: org.apache.spark.sql.AnalysisException => println(e.getErrorClass) }
null

The expected error should be ILLEGAL_SUBSTRING. It sets at

spark/sql/catalyst/src/main/scala/org/apache/spark/sql/errors/QueryCompilationErrors.scala

Line 71 in 899d3bb

errorClass = "ILLEGAL_SUBSTRING",

.

Does this PR introduce any user-facing change?

Yes, the PR changes exceptions that can be handles by users.

After the changes:

scala> try { sql("select format_string('%0$s', 'Hello')") } catch { case e: org.apache.spark.sql.AnalysisException => println(e.getErrorClass) }
ILLEGAL_SUBSTRING

How was this patch tested?

By running new test:

$ build/sbt "test:testOnly *QueryCompilationErrorsSuite"

[HyukjinKwon]

Merged to master.