[HOLD for payment 2023-05-03] Make sure internal release build are posted even if some platforms fail

[mountiny]

Problem

When we are creating the internal release of some Pr for testing, the comment is only added if all the build succeed. If one of them fails the comment is not added and its cumbersome to find the links to download the successful versions (they have been submitted to S3 bucket just fine)

Why

This wastes our time since we might need to test on just one version which has been build so this slows us down. The problem with the build can be resolved separately

Solution

Lets post the comment even if some of the builds fail.

[MelvinBot]

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[mountiny]

@staszekscp Can you please comment here so I can assign you?

[mountiny]

There will be nothing to pay though Upwork here @miljakljajic so unassigning you, thanks

[staszekscp]

Hey @mountiny! Here I am, so you can assign me!