Fix vacuous max-version assertion in pandoc oracle gate test

unit_test_format_gate_failure_contains_required_info asserted the message
contained "3.10" for both the raw detected version and the calibrated max,
but the test input's detected version line already equaled the max
boundary, so the max check passed even if the Calibrated range fragment
were broken. Assert on the full range substring instead.

Author: cderv

crates/pampa/tests/integration/test.rs

@@ -260,16 +260,15 @@ mod pandoc_oracle_gate_tests {
             message.contains("pandoc 3.10"),
             "message should contain the raw detected version line, got: {message}"
         );
-        let min_str = format!(
-            "{}.{}",
-            PANDOC_ORACLE_MIN_VERSION.0, PANDOC_ORACLE_MIN_VERSION.1
-        );
-        let max_str = format!(
-            "{}.{}",
-            PANDOC_ORACLE_MAX_VERSION.0, PANDOC_ORACLE_MAX_VERSION.1
+        let range_str = format!(
+            "Calibrated range: {}.{}\u{2013}{}.{}",
+            PANDOC_ORACLE_MIN_VERSION.0,
+            PANDOC_ORACLE_MIN_VERSION.1,
+            PANDOC_ORACLE_MAX_VERSION.0,
+            PANDOC_ORACLE_MAX_VERSION.1
         );
         assert!(
-            message.contains(&min_str) && message.contains(&max_str),
+            message.contains(&range_str),
             "message should contain the calibrated range, got: {message}"
         );
         assert!(