Alter LOGV2 behavior in the presence of missing attributes

It's my understanding that LOGV2 expressions throw when presented with attribute substitutions in the message that are not present in the overall expression. I'd like them to be fatal in debug builds and non-throwing elsewhere (perhaps logging some extra context that an attribute is missing).

Failure to do this will turn typos in log statements in exception unsafe areas of code into fatal errors in production, which feels excessive.