Frontend: CRUD actions should be restricted according to admin roles

[disalechinmay]

Description

Frontend: CRUD actions will now be restricted according to admin roles.

• Superadmin (Read, Create, Update, Delete)
• Staff Admin (Read, Create, Update, Delete)
• Admin (Read, Create, Update)
• Create Only (Read, Create)
• Read Only (Read)

Additionally there are following buttons which require the stated access levels:

• Record Payment - Update Access
• Send By Email - Create Access
• Convert To Invoice - Update Access

Related Issues

#793

Steps to Test

1. Create a readOnly admin user by navigating to the admin section
2. Login using the readOnly user that you just created. (You can also use any existing readOnly user as well)
3. Verify if you're able to create records like offers, leads, etc.

In the same manner, login using admins have other roles and verify respective CRUD actions access.
Note that we can also navigate to object create/update page directly using URL.
For example, to create an offer, we can navigate directly to <BASE_URL>/offer/create

Checklist

• I have tested these changes
• I have updated the relevant documentation
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the codebase
• My changes generate no new warnings or errors
• The title of my pull request is clear and descriptive

Additional Info

There is also this minor label issue that I've fixed on frontend/src/modules/InvoiceModule/Forms/InvoiceForm.jsx.
The label should have been 'Sent' but it was 'Pending' instead.

[salahlalami]

@disalechinmay thank you ,

could you please create new hooks called. : usePermission ,

then we can use it everywhere :

const hasPermission  = usePermission ();
// if the button for edit so will add  disable={!hasPermission('edit')} 

[disalechinmay]

@salahlalami - Thanks a lot for the suggestion! I've made the necessary changes.