Replace deprecated EvilIcons component with Icon from the component-library

### **Description**

There are many instances in the mobile codebase where the outdated `EvilIcons` component is still in use. These should be replaced with the new `Icon` component (`app/component-library/components/Icons/Icon/Icon.tsx`).

To support a smooth migration process across multiple contributors and maintain manageable PR sizes, **each pull request (PR) should focus on replacing a single instance** of the `EvilIcons` component. This makes it easier to review, test, and prevent regressions.

### **Technical Details**

- Replace one instance of `EvilIcons` with the new `Icon` component.
- Ensure all relevant props are updated to match the new API.
- Component APIs differ slightly—carefully review each usage to preserve behavior and appearance.
- Verify the replacement introduces no functional or visual regressions.

### **Acceptance Criteria**

- Only a single instance of `EvilIcons` is replaced in each PR.
- New `Icon` component is correctly integrated with proper props and logic.
- No visual or functional regressions are introduced.
- All Jest tests, e2e tests, linting, and Storybook must pass.
- PR descriptions must follow the provided template and include before/after UI screenshots.

PRs that do not meet these criteria may be closed or requested for revision.

### **Difficulty**: Intermediate

**Good first issue for:** External contributors who can run the mobile app locally and have experience with React Native, component APIs, and maintaining consistent UI and test coverage.

Search the mobile codebase for a single EvilIcons usage, then read app/component-library/components/Icons/Icon/Icon.tsx to compare the component APIs and required props. Replace only that instance while preserving its behavior and appearance; done means Jest, e2e tests, linting, Storybook, and before/after UI screenshots meet the issue criteria.

Written by the indexing model from the issue text.