match against a pattern to allow for loser order of messages

Signed-off-by: reubenmiller <reuben.d.miller@gmail.com>

Author: reubenmiller

tests/RobotFramework/tests/tedge_flows/tedge_flows.robot

@@ -280,8 +280,7 @@ Order of flow definition updates does not matter
     ${messages}    Should Have MQTT Messages
     ...    topic=te/device/main/service/tedge-mapper-local/status/flows
     ...    date_from=${start}
-    ...    message_contains=issue-3978/test.toml
-    Should Contain    ${messages[0]}    "updated"
+    ...    message_pattern=.*issue-3978/test.toml.*"status":"updated".*
 
     # Check the flow is actually working
     ${start}    Get Unix Timestamp
@@ -301,8 +300,7 @@ Order of flow definition updates does not matter
     ${messages}    Should Have MQTT Messages
     ...    topic=te/device/main/service/tedge-mapper-local/status/flows
     ...    date_from=${start}
-    ...    message_contains=issue-3978/test.toml
-    Should Contain    ${messages[0]}    "broken"
+    ...    message_pattern=.*issue-3978/test.toml.*"status":"broken".*
 
     # The new version of the flow has not been loaded because broken
     # and is no more running
@@ -325,8 +323,7 @@ Order of flow definition updates does not matter
     ${messages}    Should Have MQTT Messages
     ...    topic=te/device/main/service/tedge-mapper-local/status/flows
     ...    date_from=${start}
-    ...    message_contains=issue-3978/test.toml
-    Should Contain    ${messages[0]}    "updated"
+    ...    message_pattern=.*issue-3978/test.toml.*"status":"updated".*
 
     # And effective
     ${start}    Get Unix Timestamp