[Due for payment 2025-04-16] Fix submit logic with broken connection violation

[joekaufmanexpensify]

Action Performed:

1. Log into an account with an assigned workspace direct feed card.
2. Make sure the workspace has delayed submission enabled.
3. Scan a cash expense into the account, leaving it the report in the open state.
4. Verify you see the submit button on the report.
5. Break the card feed connection.
6. Verify you now see the broken connection violation on the report, a mark as cash button and no submit button.
7. Create a manual cash expense, which gets added to the same report as the one scanned expense with the violation.

Expected Result:

You should now see the submit button immediately on the report if it has any expenses without the broken connection violation. Submitting the report should submit only the manual cash expense with no violation and should split the scanned expense with a violation into a new report, following our existing pending expense pattern.

Actual Result:

Originally, the report had no submit button, even though one expense didn't have the violation. Then, when I tested the next day (after making no changes), the submit button appeared.

Screenshots/Videos

What I originally saw (no submit button)

2025-02-19_12-08-34.1.mp4

What I saw the next day (submit button)

2025-02-20_09-28-36.mp4

Issue Owner

Current Issue Owner: @NicMendonca

[melvin-bot]

Triggered auto assignment to @NicMendonca (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[joekaufmanexpensify]

Discussed here

[NicMendonca]

asking here - https://expensify.slack.com/archives/C07HPDRELLD/p1741187440578739?thread_ts=1739989177.668829&cid=C07HPDRELLD

[mountiny]

@narefyev91 @koko57 @VickyStash Would yo ube interested in this one? I am not sure if this is internal actually