fix(property-detail): restore build after merge resolution

[1Judah]

Summary

Repairs main so the property detail route compiles again after the conflict resolution applied while merging #1288, and removes the now-unused memo import left behind by the merge of #1293.

Problem

src/components/PropertyDetailServer.tsx currently declares PropertyDetailServer twice:

• line 26 - the original component body, still exported
• line 295 - the error-boundary wrapper added by feat(property-detail): add error boundary for property detail #1288

The wrapper renders <PropertyDetailServerInner />, but no such identifier is declared anywhere in the file. TypeScript reports this as a duplicate identifier plus Cannot find name 'PropertyDetailServerInner', so the file fails to typecheck and the app build breaks.

Separately, src/components/PropertySearch.tsx imports memo from react but never calls it: the merge of #1293 kept the import while the wrapper from the sibling error-boundary PR was chosen for the export, so the memoization call was dropped. It is dead code that trips no-unused-vars.

Changes Made

• src/components/PropertyDetailServer.tsx: renamed the first declaration to const PropertyDetailServerInner so it is the module-private implementation, leaving the error-boundary wrapper at line 295 as the single exported PropertyDetailServer.
• src/components/PropertySearch.tsx: removed the unused memo specifier from the react import.

Implementation Details

The rename is the minimal change that satisfies both errors at once: PropertyDetailServerInner becomes the component the wrapper already references, and the duplicate export disappears. The public API of the module is unchanged - the same PropertyDetailServer export with the same props, still wrapped in the ErrorBoundary added by #1288. No behaviour changes.

Prerequisite for verifying #1288's error boundary and the property detail page.

[nanaf6203-bit]

LGTM