### What happened?

After the changes made in https://github.com/SeleniumHQ/selenium/pull/11973 jar spawning is not adding the `--log-path=` flag to Chrome in the normal flow. Need to enable the `readableTimestamp` or `appendLog` flag to get it working   https://github.com/SeleniumHQ/selenium/pull/11973/files#diff-405c68a6b743ea8f4b340b5ea0c92c802a24109b4c38818335f6ca39511e2bc8R385.
What is has caused is that the chromedriver logs are append to file while going through jar causing performance issues.

### How can we reproduce the issue?

```shell
Run session on Chrome while adding logging params and opening heavy websites like Pinterest
"goog:loggingPrefs": {
  "driver": "ALL",
  "browser": "SEVERE",
  "performance": "ALL",
  "server": "ALL"
}
```


### Relevant log output

```shell
No direct logging of chromedriver flags in selenium logs found by looking around after facing performance issue.
```


### Operating System

Windows 10

### Selenium version

4.9.1

### What are the browser(s) and version(s) where you see this issue?

Chrome latest

### What are the browser driver(s) and version(s) where you see this issue?

Chromedriver related to the chrome version

### Are you using Selenium Grid?

_No response_
import java.net.MalformedURLException;
import java.net.URL;
import java.time.Duration;
import java.util.List;
import java.util.Map;
import java.util.concurrent.CompletableFuture;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.TimeUnit;
import java.util.concurrent.TimeoutException;
import java.util.concurrent.locks.ReentrantLock;
import java.util.logging.Logger;
import org.openqa.selenium.Beta;
import org.openqa.selenium.Capabilities;
import org.openqa.selenium.ImmutableCapabilities;
import org.openqa.selenium.WebDriverException;
import org.openqa.selenium.internal.Require;
import org.openqa.selenium.net.PortProber;
import org.openqa.selenium.net.UrlChecker;
import org.openqa.selenium.os.CommandLine;
/**
 * Manages the life and death of a native executable driver server. It is expected that the driver
 * server implements the <a
 * href="https:github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol">WebDriver Wire Protocol</a>.
 * In particular, it should implement /status command that is used to check if the server is alive.
 * In addition to this, it is supposed that the driver server implements /shutdown hook that is used
 * to stop the server.
 */
public class DriverService implements Closeable {