Forget job timer in case of exception or failed job

[Namoshek]

This PR fixes the remaining cases not handled by 69486d5.

I wasn't sure if having two event listeners doing the exact same thing would be preferred over a single listener supporting both events.

---

Currently, jobs throwing an exception and jobs which fail (e.g. using $this->fail()) still leak the job timer:

[2022-02-21 20:13:27] local.DEBUG: The first job is run.
[2022-02-21 20:13:27] local.DEBUG: Stopwatch {"timers":0}
[2022-02-21 20:13:27] local.DEBUG: The first job is run.
[2022-02-21 20:13:27] local.DEBUG: Stopwatch {"timers":0}
[2022-02-21 20:13:30] local.DEBUG: The first job is run.
[2022-02-21 20:13:30] local.DEBUG: Stopwatch {"timers":0}
[2022-02-21 20:13:30] local.DEBUG: The second job is started.
[2022-02-21 20:13:30] local.DEBUG: The third job throws an exception.
[2022-02-21 20:13:30] local.ERROR: Oh no! {"exception":"[object] (Exception(code: 0): Oh no! at /home/marvin/projects/laravel-horizon-memory-leak/app/Jobs/ThirdJob.php:22)"}
[2022-02-21 20:13:30] local.DEBUG: The second job is started.
[2022-02-21 20:13:30] local.DEBUG: The third job throws an exception.
[2022-02-21 20:13:30] local.ERROR: Oh no! {"exception":"[object] (Exception(code: 0): Oh no! at /home/marvin/projects/laravel-horizon-memory-leak/app/Jobs/ThirdJob.php:22)"}
[2022-02-21 20:13:33] local.DEBUG: The first job is run.
[2022-02-21 20:13:33] local.DEBUG: Stopwatch {"timers":2}
[2022-02-21 20:13:33] local.DEBUG: The second job is started.
[2022-02-21 20:13:33] local.DEBUG: The third job throws an exception.
[2022-02-21 20:13:33] local.ERROR: Oh no! {"exception":"[object] (Exception(code: 0): Oh no! at /home/marvin/projects/laravel-horizon-memory-leak/app/Jobs/ThirdJob.php:22)"}
[2022-02-21 20:13:33] local.DEBUG: The first job is run.
[2022-02-21 20:13:33] local.DEBUG: Stopwatch {"timers":3}