Fix composer hidden behind keyboard on cold start into a chat

[MelvinBot]

Explanation of Change

On a cold start (force-quit then reopen), the app can restore directly into a report via the NavigationContainer's initialState, bypassing the LHN. React Navigation does not fire onStateChange for the initial state, and updateCurrentReportID was only ever called from the onStateChange handler — so currentReportID stayed unset ('') for that first restored report.

ReportScreen gates its keyboard-avoiding view on isTopMostReportId = currentReportID === reportIDFromRoute. With currentReportID empty, isTopMostReportId is false, so shouldEnableKeyboardAvoidingView is false and the composer is not lifted above the keyboard — it ends up hidden behind it. Navigating back to the LHN and reopening the chat fires a real state change, which is why the workaround restored correct behavior.

This change seeds currentReportID from the restored root state inside onReadyWithSentry (which runs once the container is ready), so isTopMostReportId is correct on the very first report screen after a cold start. The existing updateCurrentReportID guards mean it safely no-ops when the cold start lands on a non-report screen (e.g. Inbox or Settings).

Fixed Issues

$ #97295
PROPOSAL: #97295 (comment)

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review".

Suggested manual test:

1. Open a chat (e.g. Concierge) so it is the last visited path, then force-quit the app.
2. Reopen the app so it loads directly into that chat (not the Inbox).
3. Tap the message composer.
4. Verify the composer is pushed up above the keyboard and the cursor is visible.

• Verify that no errors appear in the JS console

Offline tests

Same as tests.

QA Steps

// TODO: The human co-author must fill out the QA tests before marking this PR as "ready for review".

• 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 nothing to fix in the code — the only failing check is PR Author Checklist / checklist, and it fails purely because the checklist boxes and the Tests / QA Steps sections in the PR body aren't filled out yet.

You completed 0 out of 38 checklist items with 38 unfinished items
##[error]PR Author Checklist is not completely filled out.

That's a human-only step — I intentionally don't check those boxes or fill in the Tests/QA sections on a person's behalf, so there's no commit I can push to clear it. It'll pass once you (as the human co-author) complete the checklist and testing steps before marking the PR ready for review.

Every code-related check is green: typecheck, ESLint, React Compiler Compliance, Oxfmt, Bun tests, all test (job N) shards, Storybook, knip, and the builds. The only remaining items are baseline-perf-tests / branch-perf-tests, which are still running (informational perf comparison, not a merge blocker).

So: no fix needed on my end — the checklist just needs to be completed manually.