Fix compiling ballista in standalone mode, add build to CI

[alamb]

Which issue does this PR close?

TBD

Rationale for this change

As pointed by @thinkharderdev on #1810 #1810 (comment) compiling with ballista is currently broken (likely by #1677 and #1715):

(arrow_dev) alamb@MacBook-Pro-2:~/Software/arrow-datafusion/ballista/rust$ cargo test --no-default-features --features standalone
   Compiling etcd-client v0.8.3
   Compiling ballista-scheduler v0.6.0 (/Users/alamb/Software/arrow-datafusion/ballista/rust/scheduler)
   Compiling ballista v0.6.0 (/Users/alamb/Software/arrow-datafusion/ballista/rust/client)
error[E0061]: this function takes 3 arguments but 2 arguments were supplied
  --> ballista/rust/client/src/context.rs:93:9
   |
93 |         ballista_executor::new_standalone_executor(scheduler, concurrent_tasks).await?;
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ---------  ---------------- supplied 2 arguments
   |         |
   |         expected 3 arguments
   |
note: function defined here
  --> /Users/alamb/Software/arrow-datafusion/ballista/rust/executor/src/standalone.rs:38:14
   |
38 | pub async fn new_standalone_executor<
   |              ^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0061`.
error: could not compile `ballista` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed

What changes are included in this PR?

1. Fix compile
2. Add cargo test --features=standalone for ballista to CI
3. Disabled test_task_stuck_when_referenced_task_failed test due to Ballista standalone mode tests fail: context::tests::test_task_stuck_when_referenced_task_failed datafusion-ballista#25

Are there any user-facing changes?

No

[alamb]

This test is failing 🦜 😢 : https://github.com/apache/arrow-datafusion/issues/1840

[thinkharderdev]

yeah, that's where I got stuck as well :). I can take a look at the failing test and fix it another PR. Thanks!