[Bug] Memory acquisition failure due to inability to spill other consumers

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [x] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.

### Describe the bug

Although the spill is introduced for the writeBufferManager, but this is only valid for spilling itself. When the spark unsafeSorter holds too much memory, the buffer initial acquisition will fail. Like the following logs:

### Affects Version(s)

master

### Uniffle Server Log Output

```logtalk

```

### Uniffle Engine Log Output

```logtalk

```

### Uniffle Server Configurations

```yaml

```

### Uniffle Engine Configurations

```yaml

```

### Additional context

_No response_

### Are you willing to submit PR?

- [x] Yes I am willing to submit a PR!

Start by tracing the writeBufferManager spill path and the initial memory acquisition used alongside Spark's unsafeSorter. Reproduce the failure represented by the attached logs and verify that memory acquisition can proceed when other consumers hold too much memory by spilling them.

Written by the indexing model from the issue text.