152 segmentation dispute

[L03TJ3]

Description

Adding segmentation dispute flow to segmentation

• [x] - added generic segmentationrow
• [x] - added disputethanks
• [x] - added disputescreen
• [x] - make certificationsmap a separate hook
• [x] - style fixes for id-card

Out of scope: Analytics report, will be done in separate PR

About # (link your issue here)

150

152

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	May 14, 2024 6:07am

[sirpy]

@L03TJ3 there should not be an initial width value, i thought I made it clear. it should expand to the screen width, so we can easily see if they expand correctly

[L03TJ3]

@sirpy I will fix all the stories together in the main-pr, I am awaiting Sana's final design confirmations. After there will be a PR for 'responsivess design clean-up'