Fix search log flag query parsing

[Widthdom]

Summary

• Preserve search query literals that look like global log flags, including --log-max-size-mb, --log-format=json, and similar inline forms.
• Keep valid global log options working before and after the search query.
• Track separated global/search value options before a log-looking query so their values are not mistaken for the search query.

Root Cause

ProgramRunner stripped global log flags before dispatching to the search parser. When the query itself started with a global log option name, the pre-parser consumed it as a global option and validated the following search option as the log value.

Validation

• dotnet test tests/CodeIndex.Tests/CodeIndex.Tests.csproj --filter Issue2955 -p:UseSharedCompilation=false
• dotnet test tests/CodeIndex.Tests/CodeIndex.Tests.csproj --no-build --filter "FullyQualifiedName~ProgramRunnerTests"
• dotnet run --project tools/CodeIndex.Changelog -- check
• dotnet build CodeIndex.sln -c Release -p:UseSharedCompilation=false
• dotnet ./src/CodeIndex/bin/Debug/net8.0/cdidx.dll status --check --json
• Manual CLI repros for separated and inline log-looking query literals, valid log options before/after the query, and value-bearing global flags before the query.

A full dotnet test tests/CodeIndex.Tests/CodeIndex.Tests.csproj -p:UseSharedCompilation=false run was attempted, but it is currently blocked by the known unrelated ReferenceExtractor full-suite failure tracked in #2947.

Documentation / Changelog

• Added changelog fragment: changelog.d/unreleased/2955.fixed.md

Follow-up Candidates

• Search queries that look like non-log global flags are parsed as options #2975

Fixes #2955