require using Evaluating Matches to match server parameters

To handle non-numeric parameters, like `featureFlagQETextSearchPreview`.

Author: kevinAlbs

source/unified-test-format/unified-test-format.md

@@ -352,9 +352,9 @@ The structure of this object is as follows:
     `{ getParameter: 1, <parameter>: 1 }` command to the server using an internal MongoClient. Drivers MAY also choose
     to send a `{ getParameter: '*' }` command and fetch all parameters at once. The result SHOULD be cached to avoid
     repeated calls to fetch the same parameter. Test runners MUST apply the rules specified in
-    [Flexible Numeric Comparisons](#flexible-numeric-comparisons) when comparing values. If a server does not support a
-    parameter, test runners MUST treat the comparison as not equal and skip the test. This includes errors that occur
-    when fetching a single parameter using `getParameter`.
+    [Evaluating Matches](#evaluating-matches) when comparing values. If a server does not support a parameter, test
+    runners MUST treat the comparison as not equal and skip the test. This includes errors that occur when fetching a
+    single parameter using `getParameter`.
 
 <span id="runOnRequirement_auth"></span>
 
@@ -3416,6 +3416,9 @@ other specs *and* collating spec changes developed in parallel or during the sam
 
 ## Changelog
 
+- 2025-07-24: Require `serverParameters` use [Evaluating Matches](#evaluating-matches) behavior to compare parameters to
+    handle non-numeric values.
+
 - 2025-07-15: Clarify test runner may apply a default `cryptSharedLibPath`.
 
 - 2025-06-10: **Schema version 1.24.**