[UT][VL] Refresh TPC-H q19 plan stability golden file

[brijrajk]

Fixes #12375.

Problem

GlutenTPCHPlanStabilitySuite → tpch/q19 has been failing in spark-test-spark40 CI runs for PRs that touch Velox backend Scala files.

Root cause

GlutenPlanStabilitySuite.glutenNormalizeIds() uses the regex (?<prefix>(?<!id=)#)\\d+L? which matches any #<number> in the explain text — including TPC-H string literals. The p_brand filter in q19 uses values Brand#11, Brand#12, Brand#13 (actual TPC-H spec data values). These appear unquoted in the explain output:

EqualTo(p_brand, Brand#12)

The normalizer incorrectly treats #12 as an ExprId and remaps it sequentially. The suite code itself warns about this at line 67–68:

"Running all suites together in one JVM is recommended to avoid ExprId normalization issues where string constants (e.g., Brand#23 in TPCH q19) may collide with ExprId numbers."

What changed

The golden file was committed in #11805 (c37fee4e5, 2026-03-24). Since then 264 commits landed on main, shifting the ExprId counter. Brand#12 now normalizes to Brand#6 and _pre_1#14 shifts to _pre_1#13.

Exact diff (original vs current):

- EqualTo(p_brand, Brand#12) ... Brand#13
+ EqualTo(p_brand, Brand#6)  ... Brand#12

- _pre_1#14 / sum#15 / isEmpty#16
+ _pre_1#13 / sum#14 / isEmpty#15

Evidence that this is pre-existing

Ran GlutenTPCHPlanStabilitySuite on main at commit 6097b59a6 (2026-06-25, [MINOR][VL] Build Arrow 18 with patch for Power #12344) — without any pending PR applied:

Tests: succeeded 21, failed 1  ← q19 fails on main too
BUILD FAILURE

Then regenerated with SPARK_GENERATE_GOLDEN_FILES=1 and re-ran:

Tests: succeeded 22, failed 0
BUILD SUCCESS

Only q19/explain.txt changed. simplified.txt and all other queries (q1–q18, q20–q22) are unaffected.

Why it only surfaces on PRs touching Velox backend Scala files

spark-test-spark40 is only triggered when Velox backend Scala files are modified. Most PRs touch native C++ code, docs, or non-Velox modules and never trigger this check.

Fix

Regenerated q19/explain.txt by running GlutenTPCHPlanStabilitySuite with SPARK_GENERATE_GOLDEN_FILES=1 SPARK_ANSI_SQL_MODE=false.

A proper long-term fix (tracked in #12375) would be to make glutenNormalizeIds skip #N occurrences inside string literal contexts.

Impact

• Only gluten-ut/spark40/src/test/resources/backends-velox/gluten-tpch-plan-stability/q19/explain.txt changes
• No production code changes
• No other test queries affected

[brijrajk]

Closing — the q19 golden does not actually need refreshing.

After further investigation, the q19 "failure" only reproduces when GlutenTPCHPlanStabilitySuite is run in isolation: the TPC-H string literals Brand#11/12/13 collide with the #N ExprId normalizer in glutenNormalizeIds, and the normalized result depends on JVM-wide ExprId accumulation. CI runs the whole gluten-ut/spark40 module in one JVM, where this does not reproduce — so main's q19 golden is correct there.

Confirmed by #12151 (which touches Velox backend Scala and therefore runs spark-test-spark40 / spark-test-spark41): it is green with q19 left identical to main. This refresh would change q19 away from that CI-correct golden — which is exactly why this PR's own CI was red on q19.

The underlying normalizer limitation is tracked in #12375; a static golden refresh can't fix it reliably anyway (the normalization is run-context dependent). Closing as not needed.