feat: implement permission based UI rendering

[ManthanTerse]

Related Issue

Closes #60

Overview

Implemented a permission-based UI rendering system to control access to UI actions based on user permissions.

Changes Made

• Added centralized permission management
• Integrated Redux for global permission state handling
• Used TanStack Query for fetching and caching permissions
• Created reusable useAuthorization hook
• Added conditional rendering for permission-based UI elements
• Improved component structure and UI consistency

Permission Constants Added

export const Event_Permissions = {
  CREATE_EVENT: "event:create",
  UPDATE_EVENT: "event:update",
  DELETE_EVENT: "event:delete",
  VIEW_EVENT: "event:view",
  PUBLISH_EVENT: "event:publish",
  JOIN_EVENT: "event:join",
  LEAVE_EVENT: "event:leave",
};

Features

• Role/permission-based UI access
• Reusable authorization logic
• Optimized permission fetching with caching
• Cleaner and scalable architecture

Testing

• Verified conditional rendering for different permissions
• Checked Redux state updates and query caching
• Ensured restricted actions are hidden for unauthorized users

[gemini-code-assist]

Code Review

This pull request implements a role-based access control (RBAC) system using Redux Toolkit and React Query, introducing a centralized permissions framework with custom hooks and components. Authorization checks have been integrated across the Member, Event, Contact, and Project modules to secure pages and conditional UI elements. Feedback highlights a recurring issue where components fail to handle the isLoading state, potentially causing authorized users to see a brief 'Access Denied' flash. Additionally, improvements were suggested for the user experience in the Support and Member features to ensure that read-only states do not display misleading or non-functional UI elements.

[abhishek-nexgen-dev]

@ManthanTerse Change's Required

[ManthanTerse]

Hello @abhishek-nexgen-dev !
I've resolved it!
Please review it and merge this!
Thankyou!

[abhishek-nexgen-dev]

@ManthanTerse why you push code forcely

[ManthanTerse]

Because like 1-2 project admins told me instead of committing, push force the changes using amend @abhishek-nexgen-dev.

[abhishek-nexgen-dev]

@ManthanTerse make sure the code must written in production grade arrage every things properly make different custom hook the code must me clean modern and easy to use

• please create a doc also inside doc folder so that any one can understand why this permission based ui render use why we use it , how to use it and many more question with detail post

[ManthanTerse]

Hello @abhishek-nexgen-dev !
I have made the changes as per u told like the permission system into a cleaner production-style structure and added detailed docs.
The main pages now use a consistent boundary pattern instead of repeating manual loading/denied checks, and components like event/member/contact action areas now use usePermissionMap so the access logic is easier to read and maintain. The documentation is in docs/Permission-Based-UI-Rendering.md, covering why we use permission-based UI rendering, architecture, data flow, how to use each hook/component, production guidelines, FAQs and how to extend the system safely.

Please review it once!
And merge it!
Thankyou!!