acknowledged: false should also generate descriptive logging

[markstos]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the issue has not already been raised

Issue

In certain cases, an result of {acknowledged: false} can be returned. The official docs say vaguely that this means "things didn't go smoothly".

To resolve the issue of why it didn't go smoothly, it would be of great help if there were more logging about what exactly went wrong-- this would still be useful even if it was only emitted at the debug logging level.

#14936 is an example where a user is spending a lot of time how to resolve an "{acknowlwedged: false}" issue after an upgrade.

The more precise the logging about this could be, the faster the true root cause can found and addressed.

Ref: Here's where it's mentioned:

[markstos]

Thanks @vkarpov15 !

I updated the related discussion after I came to understand the root cause of why I was running to this tonight:

#14936