[VL] track failed UT on daily rebase

### Backend

VL (Velox)

### Bug description

https://github.com/apache/incubator-gluten/pull/9658
```
- SPARK-32614: don't treat rows starting with null char as comment
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000000000000, pid=54581, tid=196644
#
# JRE version: OpenJDK Runtime Environment 21.9 (17.0.1+12) (build 17.0.1+12-LTS)
# Java VM: OpenJDK 64-Bit Server VM 21.9 (17.0.1+12-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C 0x0000000000000000
#
# Core dump will be written. Default location: Core dumps may be processed with "/lib/systemd/systemd-coredump %P %u %g %s %t 9223372036854775808 %h" (or dumping to /__w/incubator-gluten/incubator-gluten/gluten-ut/spark35/core.54581)
#
# An error report file with more information is saved as:
# /__w/incubator-gluten/incubator-gluten/gluten-ut/spark35/hs_err_pid54581.log
#
# If you would like to submit a bug report, please visit:
# https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%208&component=java-17-openjdk
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
```

### Gluten version

_No response_

### Spark version

None

### Spark configurations

_No response_

### System information

_No response_

### Relevant logs

```bash

```

Review the failed daily-rebase context in PR #9658 and the provided JVM fatal-error log first. Reproduce or isolate the failed Velox unit test, then document the native crash's cause and make the daily rebase test pass without the SIGSEGV.

Written by the indexing model from the issue text.