[AURON #2183] Implement native support for ORC InsertIntoHiveTable writes

[weimingdiit]

Which issue does this PR close?

Closes #2183

Rationale for this change

Auron already supports native Parquet InsertIntoHiveTable writes, but ORC Hive writes still fall back to Spark’s regular execution path. This leaves native write coverage incomplete for a common Hive storage format.

This PR adds native support for ORC InsertIntoHiveTable writes so eligible Hive ORC write workloads can stay on the native path instead of falling back.

What changes are included in this PR?

This PR:

• adds native ORC sink support in the native engine
• adds planner / proto support for ORC sink execution
• adds Spark-side physical plan support for native ORC InsertIntoHiveTable
• extends AuronConverters to convert supported Hive ORC write plans to the native path
• adds ORC sink utilities for task output path generation and output completion
• preserves dynamic partition write handling on the native ORC write path
• adapts input batches to the expected ORC/Hive output schema before writing
• records output row and byte metrics for native ORC writes
• adds execution coverage in AuronExecSuite

Are there any user-facing changes?

Yes.

Hive table writes using ORC may now remain on the native execution path when they match the supported InsertIntoHiveTable write pattern, instead of falling back to Spark’s regular write execution.

How was this patch tested?

CI.

[cxzl25]

Currently Auron only has auron.enable.data.writing to control whether writing is converted to Native, but it is not enabled for different formats. It is recommended to add it for separate control.

[weimingdiit]

Good point. I changed the write gating to support separate format-level controls on top of the existing global spark.auron.enable.data.writing switch. The converter now checks spark.auron.enable.data.writing.parquet and spark.auron.enable.data.writing.orc before converting InsertIntoHiveTable.