perf(property-search): memoize handlers to reduce re-renders

[Spaully]

Summary

Reduces unnecessary re-renders in the PropertySearch component by memoizing the search box and stabilising the callback props passed down to the input and suggestion list.

This branch has been rebased onto the current main, which already carries the search error boundary merged from a sibling PR. The memoized component now sits inside that boundary, so both behaviours are preserved.

Problem

PropertySearchInner defined every handler - handleInputChange, handleSuggestionClick, handleSearchSelect, handleFocus, handleKeyDown and handleClear - inline on each render. Any re-render therefore produced fresh function identities for every handler and forced the input and suggestion buttons to reconcile even when the query and results had not changed.

Changes Made

• Imported memo and useCallback in src/components/PropertySearch.tsx.
• Wrapped each of the six handlers in useCallback with dependencies limited to what they actually read: onChange for handleInputChange and handleClear, onChange plus saveToHistory for handleSuggestionClick and handleSearchSelect, �alue for handleFocus, and suggestions, selectedIndex and handleSuggestionClick for handleKeyDown.
• Added const MemoizedPropertySearchInner = memo(PropertySearchInner) and rendered it inside the existing ErrorBoundary in the exported PropertySearch.

Implementation Details

The handlers previously changed identity on every render, which defeated memoization of anything downstream and is the main source of wasted work in this component. With the callbacks stabilised, handleKeyDown still observes the current suggestion list and highlighted index because those are declared as its dependencies. Memoization is applied to the inner component so the already-merged error boundary is preserved rather than replaced. The public props interface and rendered markup are unchanged.

Closes #1210

Closes #1209

Closes #1208

Closes #1207

[drips-wave]

@Spaully 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