making mechanical-markdown less strict but maintainig significant tests in hello-kubernetes tutorial

Signed-off-by: francesco.belacca@hotmail.it <francesco.belacca@hotmail.it>

tutorials/hello-kubernetes/README.md

@@ -265,9 +265,10 @@ Get the logs of the Node.js app:
 <!-- STEP
 expected_stdout_lines:
   - "Got a new order! Order ID: 11"
-  - "Successfully persisted state."
+  - "Successfully persisted state for Order ID: 11"
 expected_stderr_lines:
 output_match_mode: substring
+match_order: none
 name: Read nodeapp logs
 -->
 
@@ -281,11 +282,11 @@ If all went well, you should see logs like this:
 
 ```
 Got a new order! Order ID: 1
-Successfully persisted state
+Successfully persisted state for Order ID: 1
 Got a new order! Order ID: 2
-Successfully persisted state
+Successfully persisted state for Order ID: 2
 Got a new order! Order ID: 3
-Successfully persisted state
+Successfully persisted state for Order ID: 3
 ```
 
 ## Step 7 - Observe API call logs
@@ -359,6 +360,8 @@ expected_stdout_lines:
   - deployment.apps "nodeapp" deleted
   - deployment.apps "pythonapp" deleted
   - component.dapr.io "statestore" deleted
+output_match_mode: substring
+match_order: none
 -->
 
 ```bash

tutorials/hello-kubernetes/node/app.js

@@ -62,7 +62,7 @@ app.post('/neworder', async (req, res) => {
         if (!response.ok) {
             throw "Failed to persist state.";
         }
-        console.log("Successfully persisted state.");
+        console.log("Successfully persisted state for Order ID: " + orderId);
         res.status(200).send();
     } catch (error) {
         console.log(error);