[TESTING ONLY] Pin react-native-onyx to tab-sync-for-collections (Onyx PR #815)

[elirangoshen]

Explanation of Change

This is a TESTING ONLY companion PR for the react-native-onyx PR Expensify/react-native-onyx#815 ("Fix cross-tab sync for collection-root subscribers"), which $ #94839.

The only change here is pinning react-native-onyx in package.json / package-lock.json to the Onyx PR's head commit (callstack-internal/react-native-onyx#60c627e, which has the latest onyx main / v3.0.94 merged in), so the full E/App CI suite runs against the Onyx change, per the onyx repo's "Linked E/App PR" requirement. Once Onyx #803 merges and a new version is published to npm, this PR will be updated to the pinned npm version and become the version-bump PR.

What Onyx #803 fixes: Onyx cross-tab storage sync events were not delivered to collection-root subscribers (e.g. the LHN subscribing to the reports collection), so actions like pin/unpin, drafting a message, and marking read/unread performed in one tab did not sync to other open tabs. The fix broadcasts collection member changes so collection-root subscribers receive them, including chunking of large sync events and handling of legacy pre-batching events.

Manual verification was performed on web with two tabs on the same account (on App main, which includes the OnyxDerived microtask coalescing from #96785): pin/unpin, draft message, mark read/unread, and send message all synced to the idle tab, with OnyxDerived recompute counts staying at ~3-6 per action (no derived recompute storm, which was the previous failure mode before coalescing landed).

Fixed Issues

$ #94839
PROPOSAL: N/A (testing-only companion PR for the Onyx fix in Expensify/react-native-onyx#815)

Automated Tests

Automated coverage for the fix lives in the paired onyx PR (Expensify/react-native-onyx#815), in tests/unit/onyxTest.ts. This PR only pins the dependency so the full E/App CI suite runs against it.

Tests

1. Open NewDot (web) in two browser tabs and sign in to the same account in both.
2. In Tab A, pin a report from the LHN context menu. Verify in Tab B that the report becomes pinned and the LHN reorders, without refreshing.
3. In Tab A, type a draft message in a report that sits mid-list in the LHN (don't send). Verify in Tab B that the draft (pencil) icon appears on that report and the LHN reorders, without refreshing.
4. In Tab A, mark a report as unread from the context menu. Verify in Tab B that the report shows as bold/unread, without refreshing.
5. Verify neither tab freezes and no errors appear in the JS console of either tab.

• Verify that no errors appear in the JS console

Offline tests

N/A — cross-tab sync is delivered via local storage events between tabs on the same device and involves no network requests. This PR is a dependency pin only; standard offline behavior is unaffected.

QA Steps

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

[github-actions]

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️