fix(test): make sw_loguru deterministic under the collector's log sorting

The upgraded collector sorts expected and actual logs by their body text
before comparing them pairwise (apache/skywalking-agent-test-tool#59).
The two `logging`-module records are matched by `text: not null`, which
sorts as that literal string, while the records themselves led with the
default layout's timestamp — so they sorted first while their
placeholders sorted last, inverting the pairing and failing every field.

Pin a layout that leads with the logger name, which sorts after the
placeholders and orders the two records deterministically (CRITICAL
before ERROR), and reorder the expected entries to match. The formatted
path is still exercised, only the field order in the layout changes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: wu-sheng

tests/plugin/data/sw_loguru/docker-compose.yml

@@ -44,6 +44,12 @@ services:
       SW_AGENT_NAME: provider
       SW_AGENT_LOGGING_LEVEL: DEBUG
       SW_AGENT_LOG_REPORTER_LEVEL: INFO
+      # The collector sorts expected and actual logs by their body text before comparing
+      # them pairwise, so the reported text must order deterministically. The default
+      # layout leads with the timestamp, which sorts the `logging` records ahead of the
+      # loguru ones and ahead of the `not null` placeholders they are matched by; leading
+      # with the logger name keeps them last and stable. See expected.data.yml.
+      SW_AGENT_LOG_REPORTER_LAYOUT: '%(name)s [%(threadName)s] %(levelname)s - %(message)s'
 
   consumer:
     extends:

tests/plugin/data/sw_loguru/expected.data.yml

@@ -15,6 +15,11 @@
 # limitations under the License.
 #
 
+# The collector sorts expected and actual logs by their body text and then compares them
+# pairwise, so the order here is significant. The two loguru records sort by their literal
+# text; the two `logging` records are matched by `text: not null`, which sorts after them,
+# and among themselves they follow the order the collector sees - CRITICAL before ERROR,
+# given the log layout pinned in docker-compose.yml.
 logItems:
   - serviceName: provider
     logSize: 4
@@ -46,17 +51,17 @@ logItems:
         body:
           type: 'text'
           content:
-            text: not null
+            text: 'Loguru provider warning reported.'
         traceContext:
           traceId: not null
           traceSegmentId: not null
           spanId: 0
         tags:
           data:
             - key: level
-              value: ERROR
+              value: WARNING
             - key: logger
-              value: not null
+              value: loguru
             - key: thread
               value: not null
         layer: ''
@@ -66,17 +71,17 @@ logItems:
         body:
           type: 'text'
           content:
-            text: 'Loguru provider warning reported.'
+            text: not null
         traceContext:
           traceId: not null
           traceSegmentId: not null
           spanId: 0
         tags:
           data:
             - key: level
-              value: WARNING
+              value: CRITICAL
             - key: logger
-              value: loguru
+              value: not null
             - key: thread
               value: not null
         layer: ''
@@ -94,7 +99,7 @@ logItems:
         tags:
           data:
             - key: level
-              value: CRITICAL
+              value: ERROR
             - key: logger
               value: not null
             - key: thread