[VL] Noisy wrong fallback message after case-class refactor

[Yohahaha]

Backend

VL (Velox)

Bug description

== Fallback Summary ==
(1) LocalTableScan: Gluten does not touch it or does not support it
(7) NoopLeaf: Gluten does not touch it or does not support it
(8) WriteFiles: Gluten does not touch it or does not support it

== Physical Plan ==
Execute InsertIntoHadoopFsRelationCommand (11)
+- VeloxColumnarWriteFiles (10)
   :- ^ WriteFilesExecTransformer (5)
   :  +- ^ InputIteratorTransformer (4)
   :     +- ^ InputAdapter (3)
   :        +- ^ RowToVeloxColumnar (2)
   :           +- ^ LocalTableScan (1)
   +- RowToVeloxColumnar (9)
      +- WriteFiles (8)
         +- NoopLeaf (7)

24/05/27 17:32:18 WARN [main] GlutenFallbackReporter: Validation failed for plan: Execute InsertIntoHadoopFsRelationCommand[QueryId=0], due to: at least one of its children has empty output; at least one of its children has empty output

Each huge refactoring of plan conversion framework bring new concepts for user/developer, and not only need lots time to understanding new code structure and new naming, but also introduce misleading fallback messages.

In above case, I need to check code and UI more carefully to ensure the fallback log from GlutenFallbackReporter is wrong, but I really dont want to.

#5698
#5480

Spark version

None

Spark configurations

No response

System information

No response

Relevant logs

No response

[zhztheplayer]

I see there is already a list can be used to add exclusions. I can help update that list if you think is needed.

[Yohahaha]

I see there is already a list can be used to add exclusions. I can help update that list if you think is needed.

that's great, thank you!

[FelixYBW]

Can we create an exception for each fallback reason? then put the message in the exception? @zhztheplayer Let's have a sync on this.

[zhztheplayer]

A proposed fix was included in #5698. @Yohahaha