Fix onboarding loop for Track/Personal Spend path when Concierge report not in collection

When getChatByParticipants fails to find the Concierge 1:1 chat in
deprecatedAllReports (common for brand-new accounts during onboarding),
fall back to using the module-level conciergeReportIDOnyxConnect which
is populated via Onyx.connect to CONCIERGE_REPORT_ID.

Without this fallback, prepareOnboardingOnyxData returns undefined,
completeOnboarding bails out without sending COMPLETE_GUIDED_SETUP,
hasCompletedGuidedSetupFlow stays false, but navigateAfterOnboarding
still dismisses the modal. The OnboardingGuard then redirects back,
creating an infinite loop.

Made-with: Cursor

Author: roryabraham

src/libs/ReportUtils.ts

@@ -11728,9 +11728,12 @@ function prepareOnboardingOnyxData({
     // When posting to admins room and the user is in the suggestedFollowups beta, we skip tasks in favor of backend-generated followups.
     const shouldUseFollowupsInsteadOfTasks = shouldPostTasksInAdminsRoom && Permissions.isBetaEnabled(CONST.BETAS.SUGGESTED_FOLLOWUPS, betas, betaConfiguration);
     const adminsChatReport = deprecatedAllReports?.[`${ONYXKEYS.COLLECTION.REPORT}${adminsChatReportID}`];
+    const conciergeChat =
+        getChatByParticipants([CONST.ACCOUNT_ID.CONCIERGE, deprecatedCurrentUserAccountID ?? CONST.DEFAULT_NUMBER_ID], deprecatedAllReports, false) ??
+        (conciergeReportIDOnyxConnect ? {reportID: conciergeReportIDOnyxConnect} : undefined);
     const targetChatReport = shouldPostTasksInAdminsRoom
         ? (adminsChatReport ?? {reportID: adminsChatReportID, policyID: onboardingPolicyID, chatType: CONST.REPORT.CHAT_TYPE.POLICY_ADMINS})
-        : getChatByParticipants([CONST.ACCOUNT_ID.CONCIERGE, deprecatedCurrentUserAccountID ?? CONST.DEFAULT_NUMBER_ID], deprecatedAllReports, false);
+        : conciergeChat;
     const {reportID: targetChatReportID = '', policyID: targetChatPolicyID = ''} = targetChatReport ?? {};
     const targetChatType = targetChatReport?.chatType;