[Hooks] Implement Layout, Routing, and Session Lifecycle Hooks (use_breakpoint, use_navigation_beacon, use_refresh_token, use_webhook)

Problem Statement

Rusty-Framework is missing four key reactive hooks present in Ivy-Framework:

1. use_breakpoint (responsive viewport breakpoint listener)
2. use_navigation_beacon (view navigation history and routing state tracking)
3. use_refresh_token (silent background authentication token renewal)
4. use_webhook (listening to server push event webhooks)

Proposed Architecture & Design

• Implement use_breakpoint evaluating viewport width breakpoints (sm, md, lg, xl, 2xl).
• Implement use_navigation_beacon tracking route changes, referrers, and view history state.
• Implement use_refresh_token with background timer for renewing JWT sessions before expiration.
• Implement use_webhook listening to server-sent event push channels.

Acceptance Criteria

• use_breakpoint reactively updates when window or container dimensions change.
• use_navigation_beacon records route state history accurately.
• use_refresh_token fires silent renewal requests before token expiry.
• use_webhook receives push event payloads from rusty-server.

No files, tests, or entry points are named. Start by comparing the corresponding hooks in Ivy-Framework and tracing how rusty-server exposes push events and token renewal. Done means all four hooks satisfy their listed acceptance criteria, including reactive updates, route history, pre-expiry renewal, and webhook payload delivery.