fix: Update TPC-DS q36a golden file for Spark 4.0 decimal UNION widening change

[parthchandra]

Which issue does this PR close?

Running TPC-DS resulted in a schema mismatch error in q36a-v2.7

Rationale for this change

The golden file for TPC-DS v2.7 query q36a was originally generated against Spark 3.4, where DecimalPrecisionTypeCoercion.bounded() simply clamped precision/scale to the maximum (min(p, 38), min(s, 38)). This caused the UNION of decimal(37,20) and decimal(38,11) (the two branches of results_rollup) to widen to decimal(38,20).

SPARK-45905 changed the decimal least-common-type algorithm to prefer retaining integral digits over fractional digits when precision exceeds 38. The same UNION now correctly widens to decimal(38,11). Apache Spark's own TPCDSQueryTestSuite golden file reflects this.

What changes are included in this PR?

This adds a version specific golden file against Spark 4 to match the updated behavior. Also, decimal tests now also check that the schema matches with the one output by Spark.

How are these changes tested?

Running TPC-DS queries in CometTPCDSQueryBenchmark. Also unit tests.

[mbutrovich]

Thanks for the detailed PR description. This sounds like it was a journey to track down. Thanks @parthchandra!

[parthchandra]

Oh. Now the schema fails for pre-4.0 versions of Spark. So now we need a version specific set of golden files!

[parthchandra]

@mbutrovich thank you for the approval, but if you don't mind taking another look. I changed the implementation so that there is a version specific result file. Since only the one query is affected, there is only one additional file.