[Goodid] add new claim flow

[L03TJ3]

Description

We are updating the claim-flow with a new design. Because before most of the UI was handled outside of the ui-package, and everything was put into a single ClaimButton most of the logic will have to be reworked, to also align with the new wizard setup.

This PR includes:

• [x] Extend properties returned by useClaim
• [x] A claim-flow controller and wizard
• [x] new pre-claim screens with pending pools to claim from
• [x] new/reworked design for transaction list
• [x] helper for fetching recent claims
• [x] add new flow for claiming from pools
• [x] handle recent claims for pools
• [x] add error handlers
• [x] Jumping billy gif for post-claim screen
• [x] Add network icons
• [x] handle failed transactions
  • Should try to claim from all eligible pools
  • If one of them fails, show a corresponding error message using the ErrorModal (https://github.com/GoodDollar/GoodWeb3-Mono/blob/04863f889e02d42152ff5924ed9ad2e6ee737f70/packages/good-design/src/apps/ubi/wizard/ClaimWizard.tsx#L73)
  • go back to PreClaim
• [x] Bug: checkEntitlement fails (see comment)
• [x] Add contract names (Decided to keep hardcoded for now)
• [x] Transaction Details
• [x] Latest newsfeed item

Remaining todo's:

• [x] some expected styling changes
• [x] fix bug with fuse network and sdk-v2 web3provider configuration
• [x] cleanup typings

Out of scope for this PR:

• [x] add handle 'next-task' or succes modal post-claim (needs to be implemented by dapp/wallet)

About # (link your issue here)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• [ ] PR title matches follow: (Feature|Bug|Chore) Task Name
• [ ] My code follows the style guidelines of this project
• [ ] I have followed all the instructions described in the initial task (check Definitions of Done)
• [ ] I have performed a self-review of my own code
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] I have added reference to a related issue in the repository
• [ ] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
• [ ] I have added screenshots related to my pull request (for frontend tasks)
• [ ] I have pasted a gif showing the feature.
• [ ] @mentions of the person or team responsible for reviewing proposed changes

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
gooddollar-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 1, 2024 10:49pm

[L03TJ3]

@sirpy I have created a pool with address: 0xA6D77Aa130E729886C90A48e0eE539d6C6795dF7 / https://celoscan.io/address/0xa6d77aa130e729886c90a48e0ee539d6c6795df7 I have claimed succesfully in the past from it.

Currently, when trying to call checkEntitlement the following error shows: Error: call revert exception; VM Exception while processing transaction: reverted with panic code 17

Tested in hardhat console, with one of the whitelisted addresses

[sirpy]

@sirpy I have created a pool with address: 0xA6D77Aa130E729886C90A48e0eE539d6C6795dF7 / https://celoscan.io/address/0xa6d77aa130e729886c90a48e0ee539d6c6795df7 I have claimed succesfully in the past from it.

Currently, when trying to call checkEntitlement the following error shows: Error: call revert exception; VM Exception while processing transaction: reverted with panic code 17

Tested in hardhat console, with one of the whitelisted addresses

bug fixed

[sirpy]

@L03TJ3 why is this in draft? is ti ready?

[L03TJ3]

@sirpy See remaining todo's in issue description for whats left