[scan] fix scan failing to return results when there are test failures

[tahirmt]

When using test_failure! method it causes scan to skip sending the output even if fail_build is set to false

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.

Motivation and Context

Resolves #20236

Description

• While the exception is caught when fail_build option is set to false, it still causes the results to not be sent to consumers.
• To fix this I moved the fail_build definition from run_tests to scan and then used the value of fail_build to determine whether to raise the exception or to just post a ui error.

Testing Steps

Added a unit test to confirm that with fail_build set to false it returns the output from the action and that the output contains the correct values.

[joshdholtz]

Thanks so much for catching this! I added one commit to also add a check inside of the exit status code check to not raise an error. I tested this against my sample project and I was able to get the results returned as expected for when fail_build was set to both true and false.

Really appreciate the contribution! ❤️

[fastlane-bot]

Congratulations! 🎉 This was released as part of fastlane 2.206.0 🚀