feat: interview reviews base 🧱

[tomas-salgado]

Description ✏️

This PR implements the first part of the interview reviews feature.
It adds

• interview_reviews table to the database
• Fetch and list all interview reviews for a given company
• Implementation of navigation between Employees, Company Reviews, and Interview Reviews on Companies page
• Put front-end changes in _profile.companies_.$id.tsx behind a new feature flag named interview-reviews

Type of Change 🐞

• Feature - A non-breaking change which adds functionality.
• Fix - A non-breaking change which fixes an issue.
• Refactor - A change that neither fixes a bug nor adds a feature.
• Documentation - A change only to in-code or markdown documentation.
• Tests - A change that adds missing unit/integration tests.
• Chore - A change that is likely none of the above.

Checklist ✅

• I have done a self-review of my code.
• I have manually tested my code (if applicable).
• I have added/updated any relevant documentation (if applicable).

[tomas-salgado]

I decided to break up the feature into multiple PRs-it was getting too messy and this makes more sense. I'm curious if I should create stacked PRs and then not merge any until all the PRs are approved, or if I should just put the interview reviews feature behind a feature flag, so that way we can merge them in one at a time but it won't appear to members until the entire feature is complete.

UPDATE: I went with putting the front-end changes behind a feature flag interview-reviews.

I also have a PR up for the next part (feat: add interview reviews). It's in my personal fork because it's stacked on top of this branch, but once this is merged I'll be able to move the PR to the main repo here.

[tomas-salgado]

It seems there is also useSearchParams from @oyster/ui here. Curious if this should be used here?

[tomas-salgado]

One minor issue I was facing is that the navigation tabs here always show up green. This is different from the recaps page, for example, where the tab is only green if it is selected. Having trouble figuring out the issue here.

[ramiAbdou]

Going to close for now, and we'll revisit this in the future!