Call SetEnqueued before the write lock

The alternative here is outright removal due to the semantics change, but we would be breaking the IProfiledCommand interface, which has a non-nullable TimeSpan member for this.

StackExchange.Redis/StackExchange/Redis/PhysicalBridge.cs

@@ -508,6 +508,7 @@ internal bool TryEnqueue(List<Message> messages, bool isSlave)
         internal bool WriteMessageDirect(PhysicalConnection physical, Message next)
         {
             Trace("Writing: " + next);
+            next.SetEnqueued();
 
             bool result;
             lock (WriteLock)