Remove custom doubling allocation strategy in

[alamb]

Is your feature request related to a problem or challenge?

As I noted on #9025 https://github.com/apache/arrow-datafusion/pull/9025/files#r1468533266

There is a custom allocation pattern in VecAllocExt that doubles the size of the allocation each time
https://github.com/apache/arrow-datafusion/blob/d594e6257b34a5ad47112e26d41516aaeb19e6dd/datafusion/execution/src/memory_pool/proxy.rs#L39-L50

The actual rust stdlib also uses ths approach, but appears to handle overflows better :

https://github.com/rust-lang/rust/blob/fb4bca04fa1bde2f7db1b31a59e066f7bebd7fc6/library/alloc/src/vec/mod.rs#L1918-L1929

https://github.com/rust-lang/rust/blob/fb4bca04fa1bde2f7db1b31a59e066f7bebd7fc6/library/alloc/src/raw_vec.rs#L405-L436

Thus I don't know why we have our own custom doubling implementation

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

[alamb]

Interestingly, I wrote an example / test

    /// # Example:
    /// ```
    /// use datafusion_execution::memory_pool::proxy::VecAllocExt;
    /// // track how much memory is allocated in the vec
    /// let mut allocated = 0;
    /// let mut vec = Vec::new();
    /// // Push data into the vec and the accounting will be updated to reflect
    /// // memory allocation
    /// vec.push_accounted(1, &mut allocated);
    /// assert_eq!(allocated, 8); // space for 2 u32s
    /// vec.push_accounted(1, &mut allocated);
    /// assert_eq!(allocated, 8); // no new allocation needed
    ///
    /// // push more data into the vec
    /// for _ in 0..10 { vec.push_accounted(1, &mut allocated); }
    /// assert_eq!(allocated, 40); // underlying vec has space for 10 u32s
    /// assert_eq!(vec.allocated_size(), 40);
    /// ```

And this fails:

assertion `left == right` failed
  left: 48
 right: 40

Left:  48
Right: 40
<Click to see difference>

As I think the logic is incorrect