Improve error message when user attempts to settle a peeked message

[JoshLove-msft]

The current message:
The lock supplied is invalid. Either the lock expired, or the message has already been removed from the queue, or was received by a different receiver instance.

This goes along with a ServiceBusException with a FailureReason of MessageLockLost.

This isn't really accurate, because the user never had the lock to begin with. We can probably do the validation on the client and prevent the settlement on message with no LockToken. We would instead throw an InvalidOperationException if the LockToken is empty.

[ShivangiReja]

Closed with #11592