[Driver] Emit the -new-driver-path option before actual compiler arguments.

Otherwise, if it is last then it will come after the input input source-file arguments. And in immediate (`swift`) mode, things that come after input source-file arguments are considered to be arguments to the underlying script and are placed after the `--`.

Resolves rdar://75039518

Author: artemcm

tools/driver/driver.cpp

@@ -221,15 +221,16 @@ static int run_driver(StringRef ExecName,
         assert(ExecName == "swift");
         subCommandArgs.push_back("--driver-mode=swift");
       }
-      subCommandArgs.insert(subCommandArgs.end(), argv.begin() + 1, argv.end());
-
       // Push these non-op frontend arguments so the build log can indicate
       // the new driver is used.
       subCommandArgs.push_back("-Xfrontend");
       subCommandArgs.push_back("-new-driver-path");
       subCommandArgs.push_back("-Xfrontend");
       subCommandArgs.push_back(NewDriverPath.c_str());
 
+      // Push on the source program arguments
+      subCommandArgs.insert(subCommandArgs.end(), argv.begin() + 1, argv.end());
+
       // Execute the subcommand.
       subCommandArgs.push_back(nullptr);
       ExecuteInPlace(NewDriverPath.c_str(), subCommandArgs.data());