It leads to rare lock-order inversion problems if the foreground task
runner calls task destructors while holding the task runner's lock.
This currently happened when a new task was posted when the task runner
was already terminated. After normal execution we would only call the
destructor after releasing the lock anyway.

This CL ensures that the mutex is never held when calling a task
destructor.

R=mlippautz@chromium.org

Bug: 42204620
Change-Id: Ie895e5a605dff064bc5a4a90bdf1c7cdd4dc8cfe
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5718231


Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Cr-Commit-Position: refs/heads/main@{#95124}