Project should move to "Reviewed" tab when rec submitted

[hannahkates]

When an LUP submits their recommendation, we won't auto advance the milestone in CRM. However, the project should be categorized as "Reviewed" in the view.

We'll need to update the SQL queries so that:

• "To Review" tab = projects w/ the user’s milestone && !reviewed
• "Reviewed" tab = projects w/ the next LUP’s milestone || w/ the user’s milestone && reviewed

(We also might need to update the logic on the show view's top-right box.)

[allthesignals]

See the computed property hearingsSubmittedOrWaived

[andycochran]

"Submit recommendation" button should disappear after rec has been submitted

I do not understand ^this title. If a recommendation has been submitted, the project should not show up on any tabs that have buttons. Perhaps the problem is that when a recommendation is submitted, the project is not getting its status changed. This can be addressed by us automating the advancement of the milestone when the recommendation is submitted OR by the tab logic accounting for where a recommendation has been submitted (putting it in the "Reviewed" tab regardless of the current milestone).

I will update the title and confirm the business logic with our partner.

[andycochran]

Confirmed that LUP milestones should not auto-advance. Issue title/description updated accordingly.