[EPIC] A collection of tickets for improved WASM support in DataFusion

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

DataFusion can be compiled today to WASM with some care. However it is somewhat tricky and the experience could be improved.

### Describe the solution you'd like

This ticket tracks various ways we could make the experience better

### Describe alternatives you've considered

- [ ] https://github.com/apache/datafusion/issues/13715
- [x] https://github.com/apache/datafusion/issues/7652
- [ ] https://github.com/apache/datafusion/issues/9326
- [x] https://github.com/apache/datafusion/issues/13818
- [ ] https://github.com/apache/datafusion/issues/15599#issuecomment-2781114293
- [x] https://github.com/apache/datafusion/discussions/9834
- [x] https://github.com/apache/datafusion/issues/13513
- [ ] Expose more public interfaces in the Rust version to WASM bindings
- [ ] Steady release/upgrade SoP for WASM bindings (I find the python bindings can be a good example)

### Additional context

_No response_

Treat this as an umbrella issue: review the linked tickets and discussions, especially the unchecked items, to understand the separate WASM-support work. There is no single file, test, or completion condition named; done means the tracked improvements are completed or the remaining scope is explicitly resolved.

Written by the indexing model from the issue text.