feat: wire useNotifications hook to notificationApi, delete stub service

[jbeloved700]

Here's a PR description you can use:

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Wire useNotifications to notificationApi · delete stub service

Summary

Replaces the hardcoded NotificationService stub with real API calls through the existing notificationApi in
services/api.ts. The hook now drives the notifications screen rather than each managing state independently.

Changes

hooks/useNotifications.ts — rewritten

• Fetches notifications via notificationApi.list() (returns { notifications, unreadCount } in one call)
• markAsRead(id) and markAllAsRead() call the backend first; local state is only updated on success
• Exposes loading, error, and reload for the screen to consume

app/(tabs)/notifications.tsx — refactored

• Delegates all state management to useNotifications() instead of duplicating it inline
• Loading skeleton, empty state, error state with retry, and pull-to-refresh all retained

services/NotificationService.ts — deleted

• Was returning two hardcoded notifications and had comment-only stubs for markAsRead / markAllAsRead
• types/notification.ts is now the single source of Notification and NotificationsResponse types

tests/useNotifications.test.ts — updated

• Mocks notificationApi instead of the deleted stub
• Expanded from 1 test to 6: initial load, loading state, error state, markAsRead, markAllAsRead, and reload
• All 69 project tests pass

Testing

pnpm test --no-coverage # 69 passed, 9 suites
pnpm type-check # no errors

closes #551

[drips-wave]

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

[Cedarich]

LGTM