Make macros in common::test_util hygenic and not dependent on user dependencies

[AdamGS]

Which issue does this PR close?

• Closes A couple of macros in datafusion-common aren't hygenic, requiring the arrow crate as a dependency #17101.

Rationale for this change

Make both macros slightly nicer to use, and prevent some potentially confusing error messages.

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[Jefffrey]

Tested with simple example with dependency on only datafusion-common, first off main:

use datafusion_common::record_batch;

fn main() {
    let batch = record_batch!(
        ("a", Int32, vec![1, 2, 3]),
        ("b", Float64, vec![Some(4.0), None, Some(5.0)]),
        ("c", Utf8, vec!["alpha", "beta", "gamma"])
    );
}

Error:

error[E0433]: failed to resolve: use of unresolved module or unlinked crate `arrow`
 --> src/main.rs:4:17
  |
4 |       let batch = record_batch!(
  |  _________________^
5 | |         ("a", Int32, vec![1, 2, 3]),
6 | |         ("b", Float64, vec![Some(4.0), None, Some(5.0)]),
7 | |         ("c", Utf8, vec!["alpha", "beta", "gamma"])
8 | |     );
  | |_____^ use of unresolved module or unlinked crate `arrow`
  |
  = help: if you wanted to use a crate named `arrow`, use `cargo add arrow` to add it to your `Cargo.toml`
  = note: this error originates in the macro `record_batch` (in Nightly builds, run with -Z macro-backtrace for more info)

With this branch, it compiles successfully without a dependency on arrow.

LGTM 👍

[Jefffrey]

Thanks @AdamGS 🙂