Fix Memory Exhaustion in ConvertSwooleRequestToIlluminateRequest by Cleaning Up Unused Variables

[jbidad]

This pull request addresses the memory exhaustion issue occurring in the ConvertSwooleRequestToIlluminateRequest.php file by explicitly unsetting unused variables. The issue arises during the request-to-response cycle in Laravel Octane, where excessive memory consumption leads to fatal errors.

Changes Made:

• Added unset() for the additional variable $context to ensure it is cleared from memory along with other variables ($gateway, $sandbox, $request, $response, $octaneResponse, and $output).

  unset($gateway, $sandbox, $context, $request, $response, $octaneResponse, $output);

Issue Fixed:

This change prevents memory leaks or excessive memory retention, especially during high-volume or large request processing in Laravel Octane with the Swoole server. This fix resolves the memory exhaustion error reported in issue #952.

Steps to Reproduce:

1. Configure the php.ini size limitations properly (e.g., post_max_size, upload_max_filesize, memory_limit).
2. Adjust Swoole settings by configuring socket_buffer_size and package_max_length in config/octane.php.
3. Run Laravel Octane with the Swoole driver.
4. Process complex requests (e.g., file uploads or large payloads).
5. The server previously failed due to memory exhaustion, which this fix addresses by unsetting additional variables during request conversion.

---

This pull request ensures proper memory management and improves the stability of applications running under heavy workloads with Laravel Octane.