To help with debugging, we should add more info to dbcheck health log entries

• * Log the entire dbcheck command invocation, or at least log the write concern when we fail waiting for write concern or log the command invocation for error/warning entries. This would help us figure out what the invocation is without asking Atlas.- (Done in SERVER-85482)

• Add whatever batch info is available to all error/warning entries, such as batchID, count, bytes, minKey, maxKey, readTimestamp, opTime, etc. This is because currently many error/warning entries (such as write concern error) don't include much or any batch info, which makes it difficult to debug what batch bounds specifically this error occurred on
• Add whether we were a primary or secondary when logging this healthlog entry.