[ios] Enable command line parameters in release builds.

We are seeing an increased need to pass command line parameters in release
builds, both on the bots and for Test team (e.g. Franky).

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I55333de3ac89e1f379135b355080854df0cbf90d
Reviewed-on: https://chromium-review.googlesource.com/1019900Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#552078}

ios/chrome/app/startup/ios_chrome_main.mm

@@ -28,9 +28,6 @@ IOSChromeMain::IOSChromeMain() {
   web_main_runner_.reset(web::WebMainRunner::Create());
 
   web::WebMainParams main_params(&main_delegate_);
-// Copy NSProcessInfo arguments into WebMainParams in debug only, since
-// command line should be meaningless outside of developer builds.
-#if !defined(NDEBUG)
   NSArray* arguments = [[NSProcessInfo processInfo] arguments];
   main_params.argc = [arguments count];
   const char* argv[main_params.argc];
@@ -48,7 +45,6 @@ IOSChromeMain::IOSChromeMain() {
     argv[i] = argv_store[i].c_str();
   }
   main_params.argv = argv;
-#endif
 
   main_params.get_task_scheduler_init_params_callback = base::BindOnce(
       &task_scheduler_util::GetTaskSchedulerInitParamsForBrowser);