fix: service destroy listener exceptions

[tepi]

Related to #20577

[github-actions]

Test Results

1 158 files  ±0  1 158 suites  ±0   1h 34m 31s ⏱️ +46s
7 519 tests +2  7 466 ✅ +2  53 💤 ±0  0 ❌ ±0 
7 876 runs   - 7  7 814 ✅  - 7  62 💤 ±0  0 ❌ ±0 

Results for commit fd17bc7. ± Comparison against base commit 7a3569e.

♻️ This comment has been updated with latest results.

[caalador]

Looks ok, but there should perhaps be a test with multiple listeners that check that they get called even if one or more throw an exception.

[tepi]

Looks ok, but there should perhaps be a test with multiple listeners that check that they get called even if one or more throw an exception.

Good point, I'll add a test. Maybe a similar one for SessionDestroyListener as well since the logic is there already but looks like no test for that either.

[sonarqubecloud]

Quality Gate passed

Issues
36 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud