[NO QA] Fix typecheck break on main from convertToDisplayString migration

[blimpich]

Explanation of Change

main is currently red on typecheck, lint, and jest.

PR #97245 (part 14 of the convertToDisplayString migration) last ran CI on 2026-07-28 and removed the module-level convertToDisplayString import from ReportActionsUtils. PR #96901 merged after that, on 2026-07-31, and added cross-border FX payment messages that call convertToDisplayString directly. The two PRs touch different lines, so git merged them cleanly, but the identifier no longer exists — a semantic conflict that only surfaced once part 14 landed on main.

This restores the aliased CurrencyUtils import at the two call sites that build report-action copy outside of a hook context, matching how the sibling call sites in the same functions are already written, and updates the test call sites for the new signatures of getReportPreviewMessage and getIOUReportActionDisplayMessage.

No behavior changes.

Fixed Issues

$ #97722
$ #97721
$ #97720
$ #97719
$ #97718
PROPOSAL: N/A

Tests

• Verify that no errors appear in the JS console

Offline tests

N/A — no network-dependent behavior changes.

QA Steps

N/A — no user-facing change. Build-break fix only, verified by CI.

• 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
• 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 followed proper code patterns (see Reviewing the code)
  • 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 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)
• 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)
• 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 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 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 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.
• 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

N/A — no UI change.

Android: mWeb Chrome

N/A — no UI change.

iOS: Native

N/A — no UI change.

iOS: mWeb Safari

N/A — no UI change.

MacOS: Chrome / Safari

N/A — no UI change.

– written by Claude on Ben's behalf

[melvin-bot]

@QichenZhu 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]

[melvin-bot]

@rojiphil 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]

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🚧 Beamanator has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #97723.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-5af63210761-ecf5fdc-17cdc47561047243cd04ca88af44b709fb187c85/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-5af6321-ecf5fdc-5a5e360a19f2b569ba83f51efab35eb6cc07b776/index.html

Web 🕸️
https://97723.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/Beamanator in version: 9.4.49-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[MelvinBot]

🤖 I reviewed this PR against the help site files under App/docs/articles and no documentation changes are required.

Why: This is a build-break fix only. The diff restores an aliased convertToDisplayString as convertToDisplayStringUtil import in src/libs/ReportActionsUtils.ts and src/libs/ReportUtils.ts, and updates the matching test call sites in tests/unit/ReportUtilsTest.ts for the new getReportPreviewMessage / getIOUReportActionDisplayMessage signatures. The PR body itself confirms "No behavior changes" and QA is N/A.

The cross-border FX payment copy referenced here already existed on main (introduced by a separate PR), so this change neither adds nor alters any user-facing feature, screen, label, or flow that the help site documents. There's nothing new to document.

No draft docs PR was created, since there's nothing user-facing to document.

@blimpich, let me know if you'd like me to reconsider any specific flow this touches.