fix(editor): restrict query history autocomplete for performance COMPASS-8359

[Anemy]

COMPASS-8359

Adds some performance improvements to the historical autocomplete:

• Restricts the amount of suggestions to 10.
• Computes the saved queries to match at the creation of the autocomplete (rather than on type). This'll speed up the autocomplete on type, at the expensive of a bit more compute up front. We're a bit better at avoiding looping through things we know won't match now as well.
• Prevents autocompleting more than 10 fields (was 30 previously).
• Prevents autocompleting fields that, when stringified, are longer that 200 characters.
• Prevents autocompleting in arrays and nested objects. Most of the time we want this to complete on the field name so we can give fewer suggestions at the benefit of performance here.

[codeowners-service-app]

Assigned gagik for team compass-developers because nbbeeken is out of office.

[Copilot]

Pull request overview

This PR improves performance and reduces noise in the query-history autocomplete by precomputing matchable query shapes up-front and enforcing tighter limits on what’s considered for completion.

Changes:

• Limit the number of recent/favorite queries considered in the query bar (most recent 5 per category).
• Refactor query-history autocomplete to precompute simplified strings/fields once and cap results/fields/value-length for performance.
• Add tests covering new limits (max 10 suggestions, max value length 200, no nested-field matching).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
packages/compass-query-bar/src/components/option-editor.tsx	Restricts option-based query history inputs to the most recent 5 items (per recent/favorite) before autocompletion.
packages/compass-editor/src/codemirror/query-history-autocompleter.ts	Prepares queries once, limits results/fields/value sizes, and changes matching logic to use prepared data.
packages/compass-editor/src/codemirror/query-autocompleter-with-history.test.ts	Adds/updates tests to validate the new autocomplete restrictions and behavior.

[Copilot]

createQueryLabel treats falsy values (e.g. 0, empty string) as if the property is missing. This will produce an empty label for valid scalar query options like limit: 0, skip: 0, or maxTimeMS: 0. Consider checking for null/undefined (or using hasOwnProperty) instead of a falsy check so numeric zero values can still be labeled correctly.

Suggested change

	if (!query.queryProperties[propertyName]) {
	return '';
	}
	// The autocompletion uses a fuzzy search on the label, we only want to
	// auto complete property that is being edited, not all of them.
	return toJSString(query.queryProperties[propertyName]) || '';
	const value = query.queryProperties[propertyName];
	if (value === undefined || value === null) {
	return '';
	}
	// The autocompletion uses a fuzzy search on the label, we only want to
	// auto complete property that is being edited, not all of them.
	return toJSString(value) || '';

[Copilot]

prepareQueries drops any query where the target property value is falsy (if (!queryValue) return null). This will incorrectly exclude valid scalar values like 0 for limit, skip, or maxTimeMS. Also, const isObject = typeof queryValue === 'object' treats arrays as objects, so array-valued properties will still be “field”-prepared via Object.entries(...), which conflicts with the stated goal of not autocompleting arrays. Consider (1) only excluding null/undefined values, and (2) explicitly skipping Array.isArray(queryValue) (or handling arrays separately) before running Object.entries.