[FE] Batching functionality

[jkbktl]

✅ This PR:

• adds batching functionality for verification and finalization of both basic voting and featured voting (closes #79)
• recovers <NotifcationList /> for basic voting
• fixes issue when countdown stopped counting down during voting (closes #34)
• fixes issue when voting got wrong state, so it showed wrong copy (closes #62)
• fixes wrong copy for featured section when no community is featured
• fixes getActiveVotingRooms() in VotingContract, which was causing disappearing of Voting Rooms after first batch of finalization
• fixes - other small design tweaks

⚠️ Known issue:

• during finalization of the basic voting, it seems like some "votes" are lost, but it's just showing already finalized votes, after another batch it adds these votes up and so on (not ideal, not a blocker though)

[vercel[bot]]

@jkbktl is attempting to deploy a commit to the Status Team on Vercel.

A member of the Team first needs to authorize it.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
community-dapp	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 1, 2023 10:11am

[jkbktl]

There are currently two bugs:

a. This one is mentioned in the description on the top of the PR. It's related to counting votes. For some reason, during finalization phase, only "saved" votes from contract are shown. Every batch of finalization adds up new votes (included in that specific batch). You can reproduce it during every basic vote, it's visible without any specific actions.

b. Second bug happens when verification was not processes completely, meaning not all batches were sent to contract and therefore not all votes were verified during verification phase. It makes impossible for FE to evaluate verified votes in batches, because we are not able to figure it out how many votes was verified. In case it's just one batch we can use evaluatingPos to finalize voting, but even in that case it means that not all votes are counted for that specific voting. It should be reproducible by these steps (in local environment with hard limit 2 votes per batch):

1. create voting with initial vote
2. vote at least by three other accounts, which means there will be at least 2 batches
3. go through verification phase without clicking on button "verify"
4. try to finalize voting
5. it should throw an error limit is greater than votes length, because FE expects there's 4 votes (1 initial + 3 other) so it sends hard limit 2, but in reality, there's only 1 initial vote, which causes an error.