Refactor error handling to use boxed errors for DataFusionError variants

[kosiew]

Which issue does this PR close?

• Part of a series of PR to address Shrink error types sizes #16652.

Rationale for this change

This change standardizes the internal representation of several DataFusionError variants by wrapping them in Box<T>. This:

• Improves performance by reducing the memory footprint of the DataFusionError enum.
• Enables more consistent and idiomatic error handling.
• Complies with Clippy recommendations for large error enums.
• Simplifies pattern matching and variant propagation logic.

What changes are included in this PR?

• Refactored the DataFusionError enum to use Box<T> for:
  • ArrowError
  • ParquetError
  • AvroError
  • object_store::Error
  • ParserError
  • SchemaError
  • JoinError
• Updated all relevant match arms and constructors to handle boxed errors.
• Refactored error-related macros (arrow_datafusion_err!, sql_datafusion_err!, etc.) to use Box<T>.
• Adjusted test cases and error assertions for boxed variants.
• Documentation update to the upgrade guide to explain the required changes and rationale.

Are these changes tested?

Yes. These changes are covered by existing unit and integration tests, which validate correct error handling and propagation. Additional assertions were added where necessary to handle boxed variants.

Are there any user-facing changes?

No. This refactor maintains API compatibility and does not introduce breaking changes for users. Error messages and types remain consistent from the user's perspective.

[comphead]

cc @crepererum
There is another PR pending for SchemaError #16653

[alamb]

This is amazing -- thank you @kosiew

I recommend:

1. Adding a test to ensure the size of DataFusionError does not get larger (similar to the one added by @crepererum in #16653 )
2. Add a note in the upgrade guide (in #16673)

[kosiew]

@alamb

Adding a test to ensure the size of DataFusionError does not get larger (similar to the one added by @crepererum in #16653 )
Add a note in the upgrade guide (in #16673)

Added test and upgrade note.