re: followup to 14796: also call stop hook in 1 thread case

[omoerbeek]

Short description

The stop hook was not called in the threads=1 case. This looks better from a symmetry point of view as well.

Checklist

I have:

• read the CONTRIBUTING.md document
• compiled this code
• tested this code
• included documentation (including possible behaviour changes)
• documented the code
• added or modified regression test(s)
• added or modified unit test(s)

[coveralls]

Pull Request Test Coverage Report for Build 12115370868

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
• 52 unchanged lines in 15 files lost coverage.
• Overall coverage decreased (-0.005%) to 64.689%

---

Files with Coverage Reduction	New Missed Lines	%
ext/json11/json11.cpp	1	64.49%
pdns/pollmplexer.cc	1	83.66%
pdns/recursordist/aggressive_nsec.cc	2	66.02%
pdns/sstuff.hh	2	56.83%
pdns/backends/gsql/gsqlbackend.hh	2	97.71%
pdns/recursordist/test-syncres_cc2.cc	3	88.91%
pdns/stubresolver.cc	3	77.58%
pdns/packethandler.cc	3	72.48%
pdns/remote_logger.cc	3	53.36%
pdns/misc.cc	3	63.77%

Totals
Change from base Build 12087438521:	-0.005%
Covered Lines:	125857
Relevant Lines:	163646

---

💛 - Coveralls