chore: Migrate icons UI controls & actions to lazy loading

[tedward-23]

Explanation of Change

Migrate icons UI controls & actions to lazy loading

Fixed Issues

$ #75253
PROPOSAL: #75253 (comment)

Tests

Pin icon

1. Open any chat
2. Click on the chat header to open Report Details
3. Verify the Pin icon displays correctly in the promoted actions bar

Send icon

1. Open any chat
2. Type a message in the compose area
3. Verify the Send button icon displays correctly

Trashcan icon

1. Go to Settings → Workspaces → Select a workspace
2. Navigate to Per diem and click on any rate
3. Verify the Delete option shows the Trashcan icon correctly

Copy icon

1. Go to Settings → Profile
2. Verify the Copy icon displays next to your email address

QrCode icon

1. Go to Settings → Share
2. Verify the QR Code icon displays correctly on the share screen

Checkmark icon

1. Create a new expense (click + → Submit expense)
2. Tap on participant selection
3. Select a participant
4. Verify the Checkmark icon displays on the selected item

Plus icon

1. Verify the + button displays correctly in the bottom navigation bar
2. Go to Settings → Workspaces
3. Verify the New workspace option shows the Plus icon

• Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Same as tests

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Demo.mp4

[melvin-bot]

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

[melvin-bot]

@allroundexperts Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[tedward-23]

I have read the CLA Document and I hereby sign the CLA

[tedward-23]

@mollfpr

Here again. Why the rest of the workflows are not running?

[tedward-23]

@tdy2k Could you resolve the failing checks? Thanks!

Finished @mollfpr

@tdy2k I think we can have few test step to verify the migrated icons is working.

Sure.

[tedward-23]

Lets start the workflows @mollfpr

[suneox]

@tdy2k We have another conflict & eslint fail, and per our guidelines we shouldn’t force-push

App/contributingGuides/CONTRIBUTING.md

Line 181 in 1c16b77

15. Please never force push when a PR review has already started (because this messes with the PR review history)

@mollfpr The change set currently looks good. Since this PR is prone to conflicts due to the pipeline also includes import icon rule checks, once the conflicts are resolved we can proceed with this PR.

[mollfpr]

We have another conflict & eslint fail, and per our guidelines we shouldn’t force-push

@tdy2k I still didn't see any test case and no records too, could you add one please? Also, keep in mind the above comment about the force-push. Thanks!

[tedward-23]

Hello @suneox @mollfpr

Sorry for latest force-push. I made a mistake during rebase.

Merging with main now.

And adding vids

[tedward-23]

@tdy2k I still didn't see any test case and no records too, could you add one please?

Hey @mollfpr

Is testing all scope icons required, or some are enough?

Also merged with main.

[mollfpr]

@tdy2k Some are enough that easy to verify.

[mollfpr]

@tdy2k Have you follow this step https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#begin-coding-your-solution-in-a-pull-request to signed your commit?

[tedward-23]

@tdy2k Have you follow this step https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#begin-coding-your-solution-in-a-pull-request to signed your commit?

Oh forgot the -S flag when rushing

[tedward-23]

@tdy2k Some are enough that easy to verify.

Added the video @mollfpr

[mollfpr]

@tdy2k we should have all the commits signed. You can follow this step https://expensify.slack.com/archives/C01GTK53T8Q/p1710434812837899?thread_ts=1710434004.857389&cid=C01GTK53T8Q to resolve it.