ARROW-12251: [Rust] Add Ballista to CI

[andygrove]

Add cargo build and cargo test steps for Ballista. I will address fmt and clippy separately.

[github-actions]

https://issues.apache.org/jira/browse/ARROW-12251

[codecov-io]

Codecov Report

Merging #9979 (ac0e2c4) into master (81f6521) will decrease coverage by 3.86%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9979      +/-   ##
==========================================
- Coverage   82.70%   78.83%   -3.87%     
==========================================
  Files         257      285      +28     
  Lines       60486    63731    +3245     
==========================================
+ Hits        50027    50245     +218     
- Misses      10459    13486    +3027     

Impacted Files	Coverage Δ
rust/datafusion/src/physical_plan/merge.rs	68.65% <0.00%> (-8.96%)	⬇️
...t/datafusion/src/physical_plan/coalesce_batches.rs	84.07% <0.00%> (-0.89%)	⬇️
rust/datafusion/src/execution/context.rs	92.57% <0.00%> (-0.46%)	⬇️
rust/datafusion/src/execution/dataframe_impl.rs	88.88% <0.00%> (-0.22%)	⬇️
rust/parquet/src/encodings/encoding.rs	94.86% <0.00%> (-0.20%)	⬇️
rust/datafusion/src/datasource/parquet.rs	94.40% <0.00%> (-0.04%)	⬇️
rust/datafusion/tests/sql.rs	98.45% <0.00%> (ø)
rust/datafusion/src/test/mod.rs	100.00% <0.00%> (ø)
rust/datafusion/tests/dataframe.rs	100.00% <0.00%> (ø)
rust/ballista/rust/scheduler/src/lib.rs	0.00% <0.00%> (ø)
... and 46 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e20a8b2...ac0e2c4. Read the comment docs.

[andygrove]

The build fails due to:

error: failed to run custom build command for `snmalloc-sys v0.2.26`

Root cause is that cmake is not installed.

@Dandandan What is your recommendation? Do we need to use custom builder images?

[mjp41]

This came up for another project, and they added support for building snmalloc-[rs/sys] without cmake:

build_cc: use of cc crate instead of cmake (cmake still default) as builder (more platform agnostic)
SchrodingerZhu/snmalloc-rs#118

Personally, I would prefer snmalloc to be built with cmake, as that is what we test the most. But, if that is not possible for your scenario, this option is there.

[Dandandan]

Thanks @mjp41 I think that's a great option.

[andygrove]

I modified this PR to build without default features, just so we can enable CI quickly. I filed https://issues.apache.org/jira/browse/ARROW-12331 for the follow-up work for snmalloc.

[andygrove]

I confirmed that CI ran the build and tests for Ballista so will go ahead and merge this.