Test our microbenchmarks as part of CI

### Is your feature request related to a problem or challenge?

We can test our benchmarks with `cargo test --benches` which runs in debug & single iteration, just to ensure the benchmark code actually executes. Have seen instances here where some were panicking but we didn't know since we didn't often run those benchmarks

Example of one such fix recently:

- https://github.com/apache/arrow-rs/pull/10199

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

DataFusion issue:

- https://github.com/apache/datafusion/issues/24868

Start by locating the repository's CI workflow configuration and the existing Rust benchmark targets. Run `cargo test --benches` locally to confirm the expected behavior, then update CI so benchmark code is exercised and verify that the workflow completes successfully without benchmark panics.

Written by the indexing model from the issue text.