Resolver priming result should be logged

When a resolver priming attempt completes, the following message is currently logged:

resolver priming query complete

This message is identical for both successful and failed priming attempts. Consider the following log excerpts:

• successful priming attempt:

  10-Feb-2022 11:33:11.272 all zones loaded
  10-Feb-2022 11:33:11.272 running
  10-Feb-2022 11:33:19.722 resolver priming query complete

• failed priming attempt:

  10-Feb-2022 11:33:29.978 all zones loaded
  10-Feb-2022 11:33:29.978 running
  10-Feb-2022 11:33:38.432 timed out resolving '_.org/A/IN': 2001:500:9f::42#53
  10-Feb-2022 11:33:38.522 timed out resolving './NS/IN': 2001:500:9f::42#53
  10-Feb-2022 11:33:42.132 timed out resolving '_.org/A/IN': 2001:500:12::d0d#53
  10-Feb-2022 11:33:42.285 timed out resolving './NS/IN': 2001:500:12::d0d#53
  10-Feb-2022 11:33:44.685 resolver priming query complete

This can be particularly confusing when two such messages are logged close to each other, making it hard for the administrator to figure out what happened.

This is mostly a pet peeve of mine, but it seems like improving the situation would be trivial.