Usage reporting: operations that can't execute still can make interesting traces

[glasser]

In #5963 we added !!metrics.captureTraces to the condition for considering sending an operation as a trace to Studio. This makes sense for operations which start to execute (don't send something as a trace if we didn't record a trace for it!) but if the reason captureTraces is unset is because we never successfully resolved an operation, it still can be interesting to send a trace, for the sake of the Errors page.

[glasser]

The fix is released in v3.6.4.