Disable backtrace so test output is consistent

Author: teor2345

tests/ui/splat/splat-fn-ptr-tuple-fail.rs

@@ -2,9 +2,10 @@
 //! Bug #158603 regression test
 //@ run-fail
 //@ check-run-results
+//@ exec-env: RUST_BACKTRACE=0
 
 //@ normalize-stderr: "thread '.*'" -> "thread 'NAME'"
-//@ normalize-stderr: "   [0-9]*: " -> "   N: "
+//@ normalize-stderr: "note: run with.*\n" -> ""
 
 #![expect(incomplete_features)]
 #![feature(splat)]

tests/ui/splat/splat-fn-ptr-tuple-fail.run.stderr

@@ -1,15 +1,3 @@
 
-thread 'NAME' ($TID) panicked at $DIR/splat-fn-ptr-tuple-fail.rs:15:39:
+thread 'NAME' ($TID) panicked at $DIR/splat-fn-ptr-tuple-fail.rs:16:39:
 called `Option::unwrap()` on a `None` value
-stack backtrace:
-   N: panic_handler
-             at $SRC_DIR_REAL/std/src/panicking.rs:LL:COL
-   N: panic_fmt
-             at $SRC_DIR_REAL/core/src/panicking.rs:LL:COL
-   N: panic
-             at $SRC_DIR_REAL/core/src/panicking.rs:LL:COL
-   N: unwrap_failed
-             at $SRC_DIR_REAL/core/src/option.rs:LL:COL
-   N: splat_fn_ptr_tuple_fail::main
-   N: <fn() as core::ops::function::FnOnce<()>>::call_once
-note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.