If a user specifies a wc, the expectation is that upon failure a writeConcernError field is added to the response, with context regarding the failure.

However, if the user operation happens to join a filtering metadata refresh that fails to wait for write concern on a noop write, a write concern error is surfaced but no context is added to the response. This might break user applications.

It is not clear if the solution is to somehow add this context, because the fact that a noop write is being done is an implementation detail that should not be leaked, and the write concern parameters in the SSCCL are hardcoded, and might differ from user provided ones. If we surface the write concern error with context of an internal wait with different parameters, the user might be confused.