fix: Sort Messages references

Message references are now alphabetically sorted.

When an Operation has multiple messages, the resulting order depends on how the classes are parsed. This can produce slightly different results in different machines, making problematic the comparison for changes.

springwolf-core/src/main/java/io/github/springwolf/core/asyncapi/scanners/operations/OperationMerger.java

@@ -5,6 +5,7 @@
 import io.github.springwolf.asyncapi.v3.model.operation.Operation;
 
 import java.util.Collection;
+import java.util.Comparator;
 import java.util.HashMap;
 import java.util.HashSet;
 import java.util.List;
@@ -62,6 +63,9 @@ private static List<MessageReference> mergeMessageReferences(
         if (otherMessages != null) {
             messageReferences.addAll(otherMessages);
         }
-        return messageReferences.stream().toList();
+
+        return messageReferences.stream()
+                .sorted(Comparator.comparing(MessageReference::getRef))
+                .toList();
     }
 }

springwolf-core/src/test/java/io/github/springwolf/core/asyncapi/scanners/operations/OperationMergerTest.java

@@ -122,7 +122,7 @@ void shouldMergeDifferentMessageForSameOperation() {
         // then expectedMessage only includes message1 and message2.
         // Message3 is not included as it is identical in terms of payload type (Message#name) to message 2
         assertThat(mergedOperations).hasSize(1).hasEntrySatisfying(operationId, it -> {
-            assertThat(it.getMessages()).containsExactlyInAnyOrder(messageRef1, messageRef2);
+            assertThat(it.getMessages()).containsExactly(messageRef2, messageRef1);
         });
     }