GH-46177: [C++][Compute] Enable MemAllocation::PREALLOCATE for DenseUnion, SparseUnion, ListView, LargeListView, BinaryView, StringView

[andishgar]

Rationale for this change

As mentioned here, there is no preallocation strategy for the following types in compute API: ListView, LargeListView, BinaryView, StringView, DenseUnion, SparseUnion

What changes are included in this PR?

Enable MemAllocation::PREALLOCATE for the types mentioned above.

Are these changes tested?

I run the relevant unit tests.

Are there any user-facing changes?

No

• GitHub Issue: [C++][Compute] Incorrect document for MemAllocation::PREALLOCATE for string types #46177

[andishgar]

I understand that I should revise the following comments, but I’d prefer someone else to do it, as I’m not fluent in English.

arrow/cpp/src/arrow/compute/kernel.h

Lines 453 to 462 in 426d890

	// It is valid for the data to not be preallocated but the validity bitmap
	// is (or is computed using the intersection/bitwise-and method).
	//
	// For variable-size output types like BinaryType or StringType, or for
	// nested types, this option has no effect.
	PREALLOCATE,
	// The kernel is responsible for allocating its own data buffer for
	// fixed-width type outputs.
	NO_PREALLOCATE