feat(property-list): improve empty state for property list

[1Judah]

Summary

Improves the empty state for the PropertyList component. When a listing search returns no results, the virtualized grid now renders a proper empty state with a heading, explanatory copy and a "Browse Properties" action instead of an empty scroll container.

This branch has been rebased onto the current main, and while doing so it also repairs a broken reference in the same file: the virtualizer options were still reading the rowCount binding that the memoization refactor removed, leaving the grid referencing an undeclared variable. The row count now derives from the length of the chunked rows array.

Problem

VirtualizedPropertyGrid always rendered its scrollable container and ul list, so a result set with zero properties produced a large blank region with an aria-label announcing "0 items" and nothing else. Users could not tell whether the search had failed, was still loading, or had genuinely returned nothing, and were given no route back to a full listing.

Changes Made

• Imported the existing PropertyEmptyState helper from src/components/ui/EmptyState.tsx in src/components/VirtualizedPropertyGrid.tsx.
• Added an early return in the grid that renders PropertyEmptyState when properties.length === 0, passing the component's className through so surrounding layout spacing is preserved.
• Corrected the virtualizer count and its memo dependency from the removed rowCount to rows.length.

Implementation Details

The early return is placed after the existing useRef, useState, useEffect, useMemo and useVirtualizer calls, so the rules of hooks are respected and the hook sequence is identical whether the grid is empty or not. rows.length is numerically equivalent to the previous Math.ceil(properties.length / columns) calculation and is already computed immediately above, so no extra work is introduced. PropertyEmptyState is the shared empty-state component already used elsewhere in the app, which keeps the heading, description and call-to-action consistent with the rest of the search experience.

Closes #1182

Closes #1181

Closes #1180

Closes #1179

[drips-wave]

@1Judah 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