Reverts:#164231

Initiated by: jmagman

Reason for reverting: Passed a few times but is continuing to fail in prodhttps://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8721388050458438721/+/u/run_run_release_test/stdout

Original PR Author: jmagman

Reviewed By: {reidbaker}

This change reverts the following previous change:
run_debug_test_android andrun_release_test were both consistently failing because of stray stderr logging that Xcode simctl (simulator command line tool) wasn't installed.#163895 removed that logging, and these tests are now passing:
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_mokey%20run_debug_test_android/1373/overview
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_mokey%20run_release_test/3467/overview

They were originally marked bringup because they were flaky (like 10%) but while in bringup went to 100% failure due to the Xcode install issue. It looks like they really weren't flaky any more before the Xcode install issues, but erroneously the flaky issue was closed but the test wasn't marked unflaky#153830 (comment).
Moving out of bringup.

Fixes#161655

Pre-launch Checklist

• I read theContributor Guide and followed the process outlined there for submitting PRs.
• I read theTree Hygiene wiki page, which explains my responsibilities.
• I read and followed theFlutter Style Guide, includingFeatures we expect every widget to implement.
• I signed theCLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with///).
• I added new tests to check the change I am making, or this PR istest-exempt.
• I followed thebreaking change policy and addedData Driven Fixes where supported.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel onDiscord.