Split the voting up into a Project discovery phase and a voting phase

The first several votes in pairwise require you to look at the details for every project so you can understand the impact of that project... we should probably break that part out of the the later part of the voting during the round.

I'm imagining that the details will be automatically up for one project and then when the voter closes it, the details of the other project will pop up and then when they close the other details, they can vote. This phase would conclude when they have seen every project in the category once.

Then in the second phase for that category, it goes to the normal pairwise voting that we have, where the details remain hidden, with of course a feature where the user can click something to remove a project they don't like from being shown again.

Start by tracing the existing pairwise voting flow and how project details are currently shown or hidden. Define the discovery phase, its one-time-per-category completion condition, and the subsequent voting behavior before identifying the affected frontend entry points; done means voters can review every project once, then vote with an option to exclude projects from future pairs.

Written by the indexing model from the issue text.