Entities - User access : SBC and Maximus users (Phase 1)

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-12-10. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjIxMzU0)._

This epic focuses on implementing the essential roles and user access.

It includes defining and configuring user roles, establishing permission levels, and ensuring users can be assigned appropriate access based on their roles.

The goal is to provide basic access control functionality for the system, ensuring that users can only access the parts of the application that are relevant to their role, while keeping the solution simple and scalable for future iterations. This will lay the foundation for a secure and role-based user experience, with the core functionality being available ahead of full go-live.

Roles handling required for Group 1 onboarding :

- Clients (citizens and law firms) - already implemented
- Staff (BR Business team , IDIR - other) - already implemented
- SBC Contact Centre User (was BCOL Helpdesk) - new
- Service BC Field Offices - new
- Maximus HD - new

Here is the matrix of roles and features permissions to be used for implementation https://docs.google.com/spreadsheets/d/13P4ZA19lJfXJX95N5OfQMu6jYuotDH6h2hDf2DnAv0E/edit?gid=0#gid=0

The new roles BCOL HD (SBC Connect Centre), Service BC Field Offices, and Maximus SBC Contact Centre should get access to a business upon search and don't need to go through affiliation (auto-affiliation is required, the same as for Staff role currently implemented) - see https://app.zenhub.com/workspaces/raid--work-space-617c3d4cef313f001d715a7c/issues/gh/bcgov-registries/raid/658 for confirmation of the decision

**Some of the tickets below still need updated requirements. Initially, we are focusing on refactoring the code to support Auth-provided roles (instead of "if staff" in the code).**