perf(property-search): memoize derived search computations

[1Psalm]

Summary

Memoizes the derived values computed on every render of the PropertySearch component and removes a per-render array allocation from the autocomplete default, so the search box does less work on each pass.

Problem

PropertySearch recomputed showDropdown - a boolean derived from focus state, the presence of suggestions, loading state and the history flag - and rebuilt the �ctiveOptionId string on every render, including renders triggered by unrelated parent state. In addition, the autocomplete hook was destructured with a [] default, which allocated a brand new array instance on every render while the query had no data yet, invalidating any memoisation that keyed off suggestions.

Changes Made

• Imported useMemo in src/components/PropertySearch.tsx.
• Replaced the inline showDropdown and �ctiveOptionId expressions with useMemo calls keyed on [isFocused, suggestions.length, isLoading, showHistory] and [listboxId, selectedIndex] respectively.
• Added a module-level EMPTY_SUGGESTIONS constant and used it as the destructuring default for the autocomplete query.

Implementation Details

Dependencies track exactly what each derived value reads - suggestions.length rather than the array itself, since only its length affects the dropdown visibility - so the memos remain correct while avoiding recomputation on unrelated renders. The shared empty array keeps a stable identity when there are no suggestions, which is what allows consumers of suggestions to skip work. Rendered markup and autocomplete behaviour are unchanged.

Closes #1218

Closes #1217

Closes #1216

Closes #1215

[drips-wave]

@1Psalm Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[nanaf6203-bit]

LGTM