Frontend cleanup and Backend improvement (#51)

[ob22a]

• feat: reorganized the file and folder structure of the frontend

• fix: corrected the icon-container( landing page) and icon-links(Footer) style

• fix: corrected the accept terms checkbox in the signup page

• fix: corrected the displayed error message

• refactor: standardized the backend response to be wrapped in data or error

• feat: reduced the provider nesting and added dynamic title

• feat: made the cookie propertie "sameSite" dependent on env variable

• feat: added Guards to admin routes

• fix: corrected css property from a non existing "ring" to "outline"

• feat: create reducer for news and instead of fetching continously use a context that will update every 5 min

• fix: cleaned up the state and separated the hooks and the context and ensured that there is only one global state

• fix: made the navigation 1 logo title equal to navigation 2 font weight and size

• fix: corrected the code to ensure that user is not authenticated when refresh token expires

• refactor: changed the notification page background color and changed the flex direction of setting from row to column

• refactor: removed unnecessary wrapping divs and also removed useless import

• fix: corrected the officer stats incorrect response rate and replaced calculating average of average by using total value

• fix: corrected the officer count in admin manage officers page

• feat: implemented filter and positioning in the report excel

• feat: migrated from a single materialized view to 3 materialized view to reduce computation when fetching data

• feat: implemented a migration_analytics to migrate from a single MV to 3 MV

• refactor: removed the migration code after using it

• feat: corrected the frontend to include remember me option and also corrected the refresh token storage from the backend

• fix: corrected the data mapping and added fallback for excel

---

Pull Request

🔗 Linked Issue

Closes #ISSUE_NUMBER

📌 Summary

A brief summary of what this PR does.

✅ Changes Made

• List each change
• What functionality was added or fixed
• Important architectural updates

🧪 How to Test

Steps the reviewer should follow to test the feature:
1.
2.
3.

📸 Screenshots (if UI)

Attach images or GIFs.

🔒 Security Notes

• Did this PR touch authentication?
• Any new API endpoints?
• Any sensitive data risk?

🧩 Type of Change

• Feature
• Bug Fix
• Refactor
• Documentation
• Hotfix

✔️ Checklist Before Review

• Code builds successfully
• Tests added/updated
• Updated related documentation
• Linked issue included
• No console logs / debugging code