feat: add review visibility feature to faps

[TCMeldrum]

Closes UserOfficeProject/issue-tracker#1522

Description

This PR introduces the review visibility feature to faps.

Motivation and Context

This change is required to add more flexibility and control over the visibility of the reviews. It allows setting different stages when the reviews can be visible which enhances the review process.

Changes

1. A new column 'review_visibility' is added to the 'faps' table in the database. This column will hold the review visibility status.
2. The 'FapDataSource.ts' and 'FapDataSourceMock.ts' are updated to include 'review_visibility' in the 'Fap' model.
3. The 'ProposalDataSource.ts' has been updated to include a new boolean column 'call_fap_review_ended' to track the end status of the 'fap' review for a proposal.

Finally, these changes have been reflected across the backend where the 'Fap' model is used.

How Has This Been Tested?

Introduces backend tests to cover the new review visiiblity setting

Fixes Jira Issue

https://jira.esss.lu.se/browse/

Depends On

Tests included/Docs Updated?

• I have added tests to cover my changes.
• All relevant doc has been updated

[ACLay]

If there's only a few different values this should have, I wonder if a separate table which faps has a foreign key reference to might be more suitable?

[TCMeldrum]

I have refactored it to do this. I think in terms of data it is better but in terms of reability of code it is as nice, I prefered seeing Fap objects with reviewVisibility: FapReviewVisibility.PROPOSAL_REVIEWS_COMPLETE rather than reviewVisibility: 1. I couldnt see a nice way around it tho

[ACLay]

Agree it's a shame we couldn't keep the API property as the enum, but I think this looks good.