Improved CI test coverage for rust features

[alamb]

Is your feature request related to a problem or challenge?

DataFusion has many rust features (e.g. --features=parquet) and recently we hit discovered several failures for features during refactoring

• Serde feature is broken #15122
• regression: DataFusion 46 wasm compile error with parquet #15150

I reviewed the CI coverage and it is haphazard -- for example it was not clear were to add a test for #15124

Describe the solution you'd like

I would like CI coverage for all the feature flags in crates that datafusion users use

Describe alternatives you've considered

I suggest separate CI jobs for the different crates

crates:

• datafusion-substrait
• datafusion-proto
• datafusion-functions
• datafusion

For each of these crates, I would like a job that runs

1. cargo check --no-default-features
2. cargo check --no-default-features --features=<featurename>

Notes: this only runs cargo check (no need to actually create code)

Steps:

• Make per-crate jobs: Split out datafusion-substrait and datafusion-proto CI feature checks, increase coverage #15156 (review)
• REview / add full feature flag coverage for datafusion-functions crate
• REview / add full feature flag coverage for datafusion crate

Additional context

No response

[blaginin]

On a related note, maybe we want to reanimate codecov (#3679) and add a github action to prs? To ensure new code is covered

[alamb]

On a related note, maybe we want to reanimate codecov (#3679) and add a github action to prs? To ensure new code is covered

That would be great if we could do so and prove that codecov actually provides useful coverage information. The last times I ran it (a while ago) it took a long time to run and gave very non-intuitive results

[blaginin]

I'll play with it 🫡

[blaginin]

WIP PoC is here. The way I think this should work is here: blaginin#4 (comment)