Feature/claim poaps inside kiosk

[actuallymentor]

This introduces a number of visible and invisible upgrades:

• Admin button for "recalculate available codes"
• The above required a refactoring of the underlying code, which we optimised
• Minting POAPs within Kiosk, which integrates with the app, and also stores the last claimed-to address
• Adds a scalability improvement where if someone scanned and they try to claim, but at that moment someone else already claimed the code (super edge case, but when 100s of people scan at the same time it could happen) there is now a farmer-proof way for us to issue a new code to the user. This in entirely invisible to the user but means anyone who scans and is not a bot will claim a code even in very very very high throughput situations. Note that this is NOT compatible with naive mode or custom claim base urls. Those still work but do not have the same retryability.

[github-actions]

Visit the preview URL for this PR (updated for commit f06169e):

https://qr-kiosk-dev--pr138-feature-claim-poaps-vhkwwmfw.web.app

_{(expires Wed, 22 Nov 2023 17:39:31 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 2f5ca7ecd33508df1c3847295db053bb3195c8bc}

[actuallymentor]

@arvee-init posting gameplan here for merging to dev and then testing:

Todo to deploy in-kiosk minting to DEVELOPMENT

• Read through the changes: Feature/claim poaps inside kiosk #138
• Look at how minting page works: http://localhost:3000/#/mint/testing123
• Edit cypress tests so that they don't stop at checking if the mint link it correct, but also claim the demo codes at /mint/, note that all testing-xxxx codes always succeed in minting
• Check that all cypress tests clear

After deployment, test the following manually

0. Make a testing event
1. Claim a live code
2. Scan a live code without claiming
3. Does the counter show that 2 codes are unavailable?
4. Click refresh counter button int he admin panel
5. Does the counter show that only 1 code is unavailable? (Because the scanned but unclaimed code was released due to the button press)
6. Scan a claim, but do not click the mint button yet. Ninja-claim the POAP manually in a different tab, and see if it still succeeds (it should)

[arvee-init]

• Make a testing event ✅
• Claim a live code ✅
• Scan a live code without claiming ✅
• Does the counter show that 2 codes are unavailable? ✅
• Click refresh counter button int he admin panel ✅
• Does the counter show that only 1 code is unavailable? (Because the scanned but unclaimed code was released due to the button press) ✅
• Scan a claim, but do not click the mint button yet. Ninja-claim the POAP manually in a different tab, and see if it still succeeds (it should) ✅

[arvee-init]

FYI @actuallymentor all requested checks have passed:

• Admin button for "recalculate available codes" is renamed to "Refresh counter"
• Admin panel refactored
• Hot toast added
• Testing reconfigure for minting flow and Admin panel