Errors during Dequeue operation are not reporting the correct query in the exception message

[claytona-armstrong5]

While investigating an issue that we are sometimes experiencing, I noticed there seems to be a bug in the "GetMessage" method of SqlQueue.

If there is an exception, it is reporting that the query it was attempting to run was "_createQuery".
But that one is the query for creating the queue.
The query it was trying to run was actually dynamic, based on "Script.QueueDequeue"

The exception message also reports the query as "RawQuery", presumably because that class does not override the ToString() method? (Although this issue may be moot once the above was fixed?)

As an example of what I mean, we sometimes get the below error:

Shuttle.Esb.Sql.Queue.SqlQueue.Error - Could not dequeue message from queue 'sql://messaging/payments-work'. Exception: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.). Query: Shuttle.Core.Data.RawQuery

(The root cause of that error is a different matter... we are occasionally seeing very strange behaviour; it appears like successful messages from the past are getting reprocessed. I might log a separate issue for that)