Update CodeReview model to use new table

[jamescodeorg]

Update the CodeReview model to use the new table (added in #46528). This is currently branched off of the #46528 but will be rebased on staging after that is merged.

Links

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[maureensturgeon]

If the level_id and project_level_id are different, we'll send them both right? Are you waiting for the client to send the separate value to reference it here?

[jamescodeorg]

I think the client should always send both (even if they're the same). Yes, I'm waiting for the change on the client to send it projectLevelId;