Block connection of risk address

[deepthinker250]

Description

https://linear.app/opyn/issue/ENG-492/perform-aml-check-on-ui

• If the rating of address is a high risk from chain analysis, block connecting address to squeeth and show warning modal
• Else, connect address to squeeth so that user can do long, short, etc.

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Document update

How Has This Been Tested

Please describe how to test to verify the changes. Provide instructions so we can reproduce.

FE Checklist

• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] My changes generate no new warnings
• [ ] Added video recordings if it is a UI change

User Facing Checklist

• [ ] I fully understand the user problem this PR is solving
• [ ] I know who the target user is for this PR and have a deep understanding of that user
• [ ] I have tried this flow thinking from the pov of the target user for this PR
• [ ] I (or working w someone on team) have scheduled a user test for this PR (if it is a large change)

[vercel[bot]]

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

Name	Status	Preview	Updated
continuouscall	✅ Ready (Inspect)	Visit Preview	Aug 26, 2022 at 1:41PM (UTC)