fix: bracket match query display

[jackye1995]

Wrap the MatchQuery query argument in brackets so metric suffixes do not look like part of the query term.

Example verbose metrics output changes from:

MatchQuery: column=content_text, query=government: elapsed=342ms

to:

MatchQuery: column=content_text, query=[government]: elapsed=342ms

Summary by CodeRabbit

• Style

  • Updated Full Text Search (FTS) execution-plan display for MatchQuery to show the query value in square brackets (e.g., query=[...]) for the default/verbose formats.

• Tests

  • Updated FTS-related execution-plan expectation strings and snapshots to match the new MatchQuery bracketed formatting across legacy and non-legacy scenarios.

[coderabbitai]

📝 Walkthrough

Walkthrough

The MatchQueryExec display formatter now wraps query values in square brackets, and FTS execution-plan test expectations are updated accordingly.

Changes

MatchQuery display formatting

Layer / File(s)	Summary
Update MatchQuery plan formatting rust/lance/src/io/exec/fts.rs	Default and verbose output now render queries as query=[...] instead of query=....
Align FTS plan expectations rust/lance/src/dataset/mem_wal/memtable/flush.rs, rust/lance/src/dataset/scanner.rs, rust/lance/src/dataset/tests/dataset_aggregate.rs	FTS plan and aggregate test expectations now use bracketed query values across match, boost, prefilter, unindexed-row, and fast-search cases.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• lance-format/lance#7788: Refactors MatchQueryExec for element-document granularity and affects related query-plan rendering.

Suggested labels: A-format

Suggested reviewers: wjones127, wkalt, xuanwo

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: bracketing MatchQuery display output.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[wjones127]

This seems inconsistent with existing nodes. You mention that this fixes the metrics output, but there's no example in the PR description nor the unit tests, so it's hard to me to evaluate that.

[wjones127]

issue(blocking): This looks inconsistent with other nodes, which wrap arguments in brackets, not the whole line. See AggregateExec above. Should we wrap the query argument instead?

[jackye1995]

Updated to wrap only the query argument, matching the existing argument-bracketing style: MatchQuery: column=text, query=[document].