Several LOGV2 message strings were incompletely migrated away from fmt-message. This just makes them awkwardly appear in the log with unexpanded braces verbatim and it's all just noisy. There was an org-wide effort to rephrase all such messages to produce a pair of fmt-message and string-message as arguments, and some LOGV2 statements just never made the jump. After SERVER-81602, fmt-message is completely gone as a concept in LOGV2, so these will be much more conspicuous.

Maybe we could find string-message arguments that look like they contain curly-brace pairs and finish off the rephrasing effort, or generate tickets to farm this out to the relevant code-owning teams (if there are too many).