[INP] Use keyed transaction read in receipt modal to speed up Receipt-Image interaction

[MelvinBot]

Explanation of Change

The Receipt-Image interaction (tapping a receipt thumbnail to open the receipt modal) is one of the app's slowest INP interactions. The Receipt-Image Sentry label is emitted by the pressable in ReportActionItemImage that navigates to TRANSACTION_RECEIPT, so this INP measures the time from the tap until the receipt modal mounts and paints.

On mount, TransactionReceiptModalContent called useAllTransactions() and then picked a single transaction out of the result by ID. useAllTransactions() subscribes to the entire ONYXKEYS.COLLECTION.TRANSACTION collection and, in search context, additionally rebuilds a merged map of every transaction. That is collection-wide synchronous work on the critical path of the interaction, scaling with the user's total transaction count — to render a screen that only needs one transaction record.

This PR replaces that broad subscription with a single keyed read:

const [transactionMain] = useOnyx(`${ONYXKEYS.COLLECTION.TRANSACTION}${getNonEmptyStringOnyxID(transactionID)}`);

No manual search fallback is needed: COLLECTION.TRANSACTION is in CONST.SEARCH.SNAPSHOT_ONYX_KEYS, so the app's useOnyx wrapper already resolves a single TRANSACTION key from the active search snapshot. The existing draft / merge-transaction composition in the useMemo is unchanged — it's just sourced from the keyed read. The now-unused useAllTransactions import is removed.

This follows the INP Improvement Workflow guidance to drop redundant / over-broad Onyx subscriptions on interaction paths.

Fixed Issues

$ #85595
PROPOSAL: #85595 (comment)

Tests

1. Open a money request / expense report that has a receipt image attached.
2. Tap the receipt thumbnail and verify the receipt modal opens and shows the correct receipt.
3. Repeat for a PDF receipt, an eReceipt, and an odometer/distance receipt — verify each renders correctly.
4. Open a receipt from a search result (Search context) and verify the correct receipt shows.
5. Open a receipt from the transaction merge flow and verify the merge receipt is shown.
6. Open a draft receipt (during expense creation) and verify it shows.
7. Verify replace, rotate, crop, delete, and download actions still work.
8. Verify that no errors appear in the JS console.

Offline tests

Same as Tests.

QA Steps

1. Open a money request / expense report that has a receipt image attached.
2. Tap the receipt thumbnail and verify the receipt modal opens and shows the correct receipt.
3. Repeat for a PDF receipt, an eReceipt, and an odometer/distance receipt.
4. Open a receipt from a search result and from the transaction merge flow; verify the correct receipt shows in each.
5. Verify replace, rotate, crop, delete, and download actions still work.

• 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 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 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 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.
• 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

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
...alScreen/routes/TransactionReceiptModalContent.tsx	0.00% <0.00%> (ø)
... and 7 files with indirect coverage changes