Applying KYC on farmers

[maayarosama]

Description

Blocking farmers to interact with any farming features unless they're verified by kyc

Related Issues

• Apply KYC on farmers #3678

Tested Scenarios

• Created a new account on qa and go to your farms, a kyc alert was shown and I was blocked from interacting with any farmers features
• verified kyc and features were unblocked
• logged in with an already verified account features were unblocked

To consider

Preliminary Checks:

• Preliminary Checks
  • Does it completely address the issue linked?
  • What about edge cases?
  • Does it meet the specified acceptance criteria?
  • Are there any unintended side effects?
  • Does the PR adhere to the team's coding conventions, style guides, and best practices?
  • Does it integrate well with existing features?
  • Does it impact the overall performance of the application?
  • Are there any bottlenecks or slowdowns?
  • Has it been optimized for efficiency?
  • Has it been adequately tested with unit, integration, and end-to-end tests?
  • Are there any known defects or issues?
  • Is the code well-documented?
  • Are changes to documentation reflected in the code?

UI Checks:

• UI Checks
  • If a UI design is provided/ does it follow it?
  • Does every button work?
  • Is the data displayed logical? Is it what you expected?
  • Does every validation work?
  • Does this interface feel intuitive?
  • What about slow network? Offline?
  • What if the gridproxy/graphql/chain is failing?
  • What would a first time user have a hard time navigating here?

Code Quality Checks:

• Code Quality Checks
  • Code formatted/linted? Are there unused imports? .. etc
  • Is there redundant/repeated code?
  • Are there conditionals that are always true or always false?
  • Can we write this more concisely?
  • Can we reuse this code? If yes, where?
  • Will the changes be easy to maintain and update in the future?
  • Can this code become too complex to understand for other devs?
  • Can this code cause future integration problems?

Testing Checklist

• Does it Meet the specified acceptance criteria.
• Test if changes can affect any other functionality.
• Tested with unit, integration, and end-to-end tests.
• Tested the un-happy path and rollback scenarios.
• Documentation updated to meet the latest changes.
• Check automated tests working successfully with the changes.
• Can be covered by automated tests.

General Checklist

• Tests included
• Build pass
• Documentation
• Code format and docstring
• Screenshots/Video attached (needed for UI changes)

[ehab-hassan]

@maayarosama Good work just small comments, follow the Figma file
https://www.figma.com/proto/b50GilnYwLrhwOUIhfzHNA/dashboard-Nav?node-id=1494-2832&t=cDL2ZXkzDQjEFLxH-0&scaling=contain&content-scaling=fixed&page-id=0%3A1&starting-point-node-id=124%3A196

or this as a guide

remove the button from the alert and add it below the image as we Agreed with @AhmedHanafy725
Add some margin-top to the image so it is at the center.

waiting for more test scenarios