Missing trace when converting HTTP Timeout to 503

[ealsur]

When we convert HTTP timeouts to a 503 response, we are failing to pass the trace parameter.

azure-cosmos-dotnet-v3/Microsoft.Azure.Cosmos/src/HttpClient/CosmosHttpClientCore.cs

Lines 381 to 398 in e5972ac

	if (isOutOfRetries || !timeoutPolicy.IsSafeToRetry(requestMessage.Method))
	{
	// throw current exception (caught in transport handler)
	string message =
	$"GatewayStoreClient Request Timeout. Start Time UTC:{startDateTimeUtc}; Total Duration:{(DateTime.UtcNow - startDateTimeUtc).TotalMilliseconds} Ms; Request Timeout {requestTimeout.TotalMilliseconds} Ms; Http Client Timeout:{this.httpClient.Timeout.TotalMilliseconds} Ms; Activity id: {System.Diagnostics.Trace.CorrelationManager.ActivityId};";
	e.Data.Add("Message", message);
	if (timeoutPolicy.ShouldThrow503OnTimeout)
	{
	throw CosmosExceptionFactory.CreateServiceUnavailableException(
	message: message,
	headers: new Headers()
	{
	ActivityId = System.Diagnostics.Trace.CorrelationManager.ActivityId.ToString(),
	SubStatusCode = SubStatusCodes.TransportGenerated503
	},
	innerException: e);
	}

CosmosExceptionFactory.CreateServiceUnavailableException has a trace parameter that we are not passing.

This generates empty diagnostics:

Response status code does not indicate success: ServiceUnavailable (503); Substatus: 20003; ActivityId: xxxxx; Reason: (GatewayStoreClient Request Timeout. Start Time UTC:xx/xx/xxxx xx:xx:xx xx; Total Duration:65013.1998 Ms; Request Timeout 65000 Ms; Http Client Timeout:65000 Ms; Activity id: xxxx;);; 
Diagnostics:{"Summary":{},"name":"NoOp","start time":"00:00:00:000","duration in milliseconds":0}