If updating a history store entry fails, WiredTiger should log an always-visible warning or an error for any unexpected failure that causes the upper-level operation to fail.

For example, calling WT_SESSION::checkpoint sometimes returns ENOENT for no apparent reason, especially on release builds, as they have regular asserts disabled. It is strongly suspected that such errors often come from updating the history store during reconciliation, which is often triggered by a checkpoint.

Such errors are very hard to reproduce, and as there is often no information about from where the error originated on release builds, these failures are very hard to diagnose.

We should add verbose warnings or errors when such errors happen, which will both help us to see the origin of the error and provide any additional information to help with subsequent debugging.