[VL] Surface full Velox exception context in native plan validation JNI

[Yao-MR]

What changes are proposed in this pull request?

PlanEvaluatorJniWrapper::nativeValidateWithFailureReason only catches
std::invalid_argument. Any other native error - including a VeloxException
thrown from inside SubstraitToVeloxPlanValidator::validate - falls through
to JNI_METHOD_END, which converts it to a Java GlutenException using only
e.what(). The JVM therefore receives the bare error message (e.g.
"duplicated rule") with no information about which component failed,
no errorSource / errorCode, no failing expression, no native stack trace.

This PR adds an explicit VeloxException catch in the JNI handler that logs
the full diagnostic context to LOG(ERROR) and then re-throws so the existing
JNI_METHOD_END path is preserved verbatim:

How was this patch tested?

mock exception and test the ut.

related ISSUE: #12141

Was this patch authored or co-authored using generative AI tooling?