Fix: use converted JPEG for HEIC receipts on Submit share tab

[MelvinBot]

Explanation of Change

On iOS, sharing a HEIC image into the app and using the Submit tab created the expense but failed to attach the receipt — the backend rejected it with Unsupported file type: image/heic. The chat Share tab worked because it uploads the converted JPEG.

SubmitDetailsPage already computes the branch-aware fileUri/fileName/fileType, which resolve to the converted JPEG (from VALIDATED_FILE_OBJECT) for shares that need conversion, and to the raw attachment otherwise. But it then re-derived sharedFileSource/sharedFileName/sharedFileType from currentAttachment with ?? fileUri fallbacks. Since currentAttachment.content/.mimeType are always populated for a shared file, those fallbacks were dead code and the raw .heic path/image/heic type always won — flowing into the seeded receipt and performUpload → readFileAsync.

This change:

1. Uses the already-correct fileUri/fileName/fileType directly for the receipt source/name/type, mirroring ShareDetailsPage. Non-HEIC shares are unchanged (there fileUri === currentAttachment.content).
2. Blocks confirm in performUpload until the async conversion has landed in VALIDATED_FILE_OBJECT for shares that need validation (shouldUsePreValidatedFile && !validFilesToUpload), so a fast tap can't submit the raw file. The early return keeps clearing isConfirming so the button isn't stuck and a retry succeeds once the JPEG is ready.

Added regression tests in tests/ui/SubmitDetailsPageTest.tsx covering both the converted-upload behavior and the confirm guard.

Fixed Issues

$ #95824
PROPOSAL: #95824 (comment)

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

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

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

[MelvinBot]

I looked into the failing checks. There's no code-level failure to fix — every functional check now passes:

• ✅ typecheck, ESLint check, Oxfmt check, React Compiler Compliance
• ✅ All 8 test jobs (including the new tests/ui/SubmitDetailsPageTest.tsx)
• ✅ Bun tests, Storybook tests, spellcheck, all build jobs, perf tests, Check for unused styles, Compare knip issues against main

The only red check is PR Author Checklist / checklist, and it's failing for non-code reasons:

❌ PR Author Checklist is not completely filled out. Please check every box to verify you've thought about the item.
⚠️ Could not verify engineering membership for MelvinBot. Assuming they are not a member.

That check just requires the checklist boxes in the PR description to be ticked and the Tests/QA sections to be filled in. Those are human certification steps — I won't tick them on someone's behalf, so I have nothing to push here.

To get this check green, thelullabyy should complete the PR Author Checklist and fill in the Tests / QA Steps sections in the description (or add [No QA] to the title if QA isn't applicable).