Frontend user roles integration

[NSUWAL123]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

• Related to Hide/unhide the buttons from frontend based on user roles #1068
• Related to User Roles: Create user roles in frontend for organization admin #1161
• Related to Allow super admin or project creator to unlock task or revert to ready for mapping #2181

Describe this PR

• Hide/Unhide buttons, provide access to functionality and pages based on user roles

Screenshots

N/A

[spwoodcock]

Instead of defining these based on the action type, could they be defined based on the access level?

We shouldn't need many in that scenario:

export function isOrgManager(id: number) {
  const authDetails = CoreModules.useAppSelector((state) => state.login.authDetails);
  return (
    authDetails?.role === user_roles.ADMIN || (authDetails?.orgs_managed && authDetails?.orgs_managed?.includes(id))
  );
}

isProjectManager

isFieldManager

isAdmin

[spwoodcock]

This is good for orgs_managed: null 👍

If for some reason the backend response changed to be orgs_managed: [] this would evaluate true, but the next check for the specific org id should still prevent access.

[NSUWAL123]

@spwoodcock please have a look! Updated according to your suggestion.

[spwoodcock]

Looks good to me!

Useful reference: https://docs.google.com/spreadsheets/d/1crWztvXvuewE8Zv-qxbv0t_-eYHUqSlrJQgeto8kmf4