fix(node-runtime): abandon message on InvalidOperationException

The MessageProcessingService was catching InvalidOperationException
without abandoning the message, causing test failures. Added abandon
logic to the InvalidOperationException handler to match the behavior
of the generic Exception handler.
Fixes: ProcessMessage_WithUnexpectedException_ShouldAbandon test

Author: dylan-mccarthy

src/Node.Runtime/Services/MessageProcessingService.cs

@@ -293,6 +293,20 @@ private async Task ProcessSingleMessageAsync(ReceivedMessage message, Cancellati
             stopwatch.Stop();
             _logger.LogError(invalidOpEx, "Invalid operation while processing MessageId={MessageId}", message.MessageId);
 
+            // For unexpected InvalidOperationExceptions, abandon the message for retry
+            try
+            {
+                await _inputConnector.AbandonMessageAsync(message, cancellationToken);
+            }
+            catch (Azure.Messaging.ServiceBus.ServiceBusException abandonEx) when (abandonEx.Reason == Azure.Messaging.ServiceBus.ServiceBusFailureReason.MessageLockLost)
+            {
+                _logger.LogWarning("Cannot abandon MessageId={MessageId} - lock already lost", message.MessageId);
+            }
+            catch (InvalidOperationException)
+            {
+                _logger.LogWarning("Cannot abandon MessageId={MessageId} - already settled", message.MessageId);
+            }
+            
             activity?.SetStatus(ActivityStatusCode.Error, invalidOpEx.Message);
             activity?.AddEvent(new ActivityEvent("exception",
                 tags: new ActivityTagsCollection