refactor: centralize routing and eliminate duplicate sources

[Nacho1499]

Closes #79

PR Description:
This PR addresses issue #79 by eliminating duplicate routing sources between the main application engine and the routing metadata configurations. All runtime paths, layout components, and navbar hooks have been consolidated into a single absolute source of truth.

Changes Made:
**Unified Configuration: Created as the single source of truth for all routes. Brought the static sub-section assembly and the fallback components inside it.src/config/routes.tsxHomeNotFound.

**Safe Lazy Loading: Implemented robust type-safe wrapper modules capable of handling both named and default component file exports flawlessly.lazy().

**Streamlined App.tsx: Removed all hardcoded or split route mapping configurations from . It now acts purely as a delivery engine that loops over dynamically inside .src/App.tsxrouteConfig

**Strict Type Alignment: Resolved compile-time errors regarding type imports () and removed local JSX parser errors by shifting the configurations into a clean format.verbatimModuleSyntax.tsx.

Verification Checklist:
[x] Only one route definition source is used at runtime.
[x] Both the layout page routing () and header navigation arrays () derive data from the same exact configuration set.src/App.tsxgetNavItems.
[x] Breaking modifications/path changes in a single location can no longer trigger a desynchronization regression or accidental 404 errors.

[drips-wave]

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

[Nacho1499]

conflict resolved

[Mkalbani]

@Nacho1499 please resolve conflict

[Nacho1499]

conflict resolved boss