feat: add macros for DataFusionError variants

[Chen-Yuan-Lai]

Which issue does this PR close?

• Closes Add missing error macro #15491.

Rationale for this change

What changes are included in this PR?

As #15491 says, add two macros for

• External
• ExecutionJoin

Moreover, the macro for ResourcesExhausted already existed, so we don't need to add it in the PR

Are these changes tested?

Are there any user-facing changes?

[comphead]

wasn't there any current usage of this error types it to replace with macros?

[Chen-Yuan-Lai]

Hi @comphead, I noticed that using make_error! isn't suitable for these error variants because External and ExecutionJoin are designed to wrap original error objects, not just error messages.

Instead, I've implemented custom macros for External and ExecutionJoin errors, similar to #15796, and replaced a few use cases as examples. Should we replace all the cases?

[comphead]

The key point of this macros is preserving backtrace which makes debugging easier if you got an error from datafusion among multiple layers of processing.

The variant below is for non string errors preserving the backtrace

#[macro_export]
macro_rules! schema_err {
    ($ERR:expr $(; diagnostic = $DIAG:expr)?) => {{
        let err = $crate::error::DataFusionError::SchemaError(
            $ERR,
            Box::new(Some($crate::error::DataFusionError::get_back_trace())),
        );
        $(
            let err = err.with_diagnostic($DIAG);
        )?
        Err(err)
    }
    };
}