Fix HTTP batch cleanup after callback exceptions

[Nipun404]

Summary

• ensure HTTP client batches always clean up internal state when a batch callback throws
• add a regression test covering exceptions thrown from the progress callback

Problem

Illuminate\Http\Client\Batch::send() marked the batch as in progress before dispatching requests, but only reset inProgress and finishedAt at the normal end of the method.

If a user-supplied batch callback like progress(...) threw an exception, execution exited send() early and skipped that cleanup. This left the batch object in a stale state where it still appeared to be running.

Fix

• wrap the main send() flow in try / finally
• keep exception behavior unchanged
• always reset:
  • finishedAt
  • inProgress