RLS Policies - Registration app

[dleard]

blocked by #486

Description:

Add all the necessary RLS policies for the models in the registration app. Use the example in the POC PR bcgov/cas-registration#2558 as a guide on how to apply policies.

Development Checklist:

• All models that require RLS policies have policies applied using the RLS app classes
• All models with RLS policies have tests that confirm the policy logic

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• User story is included
• User role and type are identified
• Acceptance criteria are included
• Wireframes are included (if required)
• Design / Solution is accepted by Product Owner
• Dependencies are identified (technical, business, regulatory/policy)
• Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

• Acceptance criteria are tested by the CI pipeline
• UI meets accessibility requirements
• Configuration changes are documented, documentation and designs are updated
• Passes code peer-review
• Passes QA of Acceptance Criteria with verification in Dev and Test
• Ticket is ready to be merged to main branch
• Can be demoed in Sprint Review
• Bugs or future work cards are identified and created
• Reviewed and approved by Product Owner

Blocked By/Blocking

Notes:

[dleard]

Added the attn: developer tag on this one as I think we'll need to collaborate with registration devs to hammer out what the policies should be for these models. cc @pbastia @andrea-williams @Sepehr-Sobhani