Fix; Duplicate Navigation Implementation

[Obiajulu-gif]

Summary

This pr closes #46

• Consolidated dual navigation systems by adopting expo-router as the primary file-based routing solution.
• Migrated global application logic (socket connections, notification listeners, and request monitoring) from App.tsx into the root app/_layout.tsx.
• Refactored app/(tabs)/_layout.tsx to utilize MobileTabBar and MobileHeader components, maintaining UI parity with the previous drawer-based design.
• Mapped all existing screens in src/screens/ to the app/ directory, including custom parameter-handling wrappers for Profile, CourseViewer, and Quiz.
• Eliminated redundant navigation code by deleting App.tsx, AppNavigator.tsx, and SwipeableNavigation.tsx.

Testing

• Verified app initialization (sockets, notifications) launches correctly via app/_layout.tsx.
• Verified tab navigation functionality using the custom MobileTabBar.
• Verified stack navigation and parameter passing for CourseViewer and Quiz screens.
• Confirmed that deleting legacy navigation files does not impact the new expo-router workflow.

Checklist

• Linked issue or backlog item (Choose ONE navigation approach)
• Navigation behavior and route structures are described clearly
• Routing consolidated exclusively to the app/ directory
• Scope stays limited to navigation consolidation concerns

[drips-wave]

@Obiajulu-gif 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

[RUKAYAT-CODER]

Kindly resolve conflict