Disable spill to disk globally

[thinkharderdev]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and why for this feature, in addition to the what)

Certain operators (Sort, HashJoin, etc) support spill-to-disk if they have to buffer too much data in memory. For some use cases this may not be desired and it would be better to have the query fail.

It would be great if this was configurable in the SessionConfig and if the flag was set to false, any operator which uses a MemoryConsumer would fail instead of trying to spill to disk.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Add an enable_disk_spill to the SessionConfig (which can default to true for backwards compat). Current implementations of MemoryConsumer should respect this flag and fail when spill is called if disk spill is disabled.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

This could be configured on a per-operator basis but I think it probably is something that needs to be either globally disabled or enabled in the vast majority of use cases.

Additional context
Add any other context or screenshots about the feature request here.

[andygrove]

It would be great if we could use the key-value based configuration framework introduced recently in DataFusion. It allows us to generate documentation for the user guide.

https://arrow.apache.org/datafusion/user-guide/configs.html

[alamb]

I think @tustvold implemented this in #4330