### 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_
process.setEnvironmentVariables(environment);
      process.copyOutputTo(getOutputStream());
      process.executeAsync();
      if (!process.waitForProcessStarted(timeout.toMillis(), TimeUnit.MILLISECONDS)) {
        throw new WebDriverException("Timed out waiting for driver process to start.");
      }
      CompletableFuture<StartOrDie> serverStarted =
          CompletableFuture.supplyAsync(
              () -> {
                waitUntilAvailable();
                return StartOrDie.SERVER_STARTED;
              },
              executorService);
      CompletableFuture<StartOrDie> processFinished =
          CompletableFuture.supplyAsync(
              () -> {
                try {
                  process.waitFor(getTimeout().toMillis());
                } catch (org.openqa.selenium.TimeoutException ex) {
                  return StartOrDie.PROCESS_IS_ACTIVE;
                }
                return StartOrDie.PROCESS_DIED;
              },
              executorService);
      try {
        StartOrDie status =
            (StartOrDie)
                CompletableFuture.anyOf(serverStarted, processFinished)
                    .get(getTimeout().toMillis() * 2, TimeUnit.MILLISECONDS);
        switch (status) {