Fix bug in filter descriptions for not() with exact + partial submatches

If you entered 'not(header' it matches header/headers, and it always
selected 'headers' for the description as the longest option, even
though it's clearly the worst. We now prioritise fuller matches
significantly (mildly hacky approach, but should be fine in practice I
think).

Author: pimterry

src/model/filters/search-filters.ts

@@ -1402,7 +1402,11 @@ class NotFilter extends Filter {
                 match: matchSyntax(filter.filterSyntax, innerValue, 0)
             })).filter(({ match }) => (match?.partiallyConsumed || 0) > 0);
 
-            const bestMatch = _.maxBy(matches, m => m.match!.partiallyConsumed);
+            const bestMatch = _.maxBy(matches, m =>
+                // Use both, to ensure that fuller matches go before more partial
+                // matches (e.g. header/headers) when both are available
+                m.match!.fullyConsumed + m.match!.partiallyConsumed
+            );
             const innerDescription = bestMatch
                 ? bestMatch.filter.filterDescription(innerValue, isTemplate)
                 : '...';

test/unit/model/filters/search-filter-integration.spec.ts

@@ -1581,6 +1581,7 @@ describe("Search filter model integration test:", () => {
                 ["not(", "exchanges that do not match a given condition"],
                 ["not(error", "excluding requests that weren't transmitted successfully"],
                 ["not(head", "excluding exchanges by all header values"],
+                ["not(header", "excluding exchanges by a specific header"],
                 ["not(query^=?abc)", "excluding requests with a query string starting with ?abc"],
                 ["not(hostname*=", "excluding requests to a hostname containing a given value"],
                 ["not(method=POST)", "excluding POST requests"]