fix: Allows clients to expect that query performance results have been logged before they receive a response

[rcaudy]

Defer response messaging to onSuccess for all ExportBuilders that use QueryPerformanceRecorder. This allows clients to expect that query performance results have been logged before they receive a response.

Change summary:

• Adjust all SessionState.ExportBuilder uses that set a QueryPerformanceRecorder to use onSuccess for response delivery if possible
• Exclusions: DoExchange subscriptions and async input table operations
• Note: batch already used onSuccess, but completion now happens after performance results are reported
• Some cleanup to GrpcUtil usage

[nbauernfeind]

LGTM, waiting for a ping from @niloc132 before approving in case he wants a final look before the merge.