### What happened?

Have noticed that sometimes  Selenium Manager fails to configure driver executable path if tests are run in parallel.

Environment: 
Java: Oracle OpenJDK 17.0.2
Gradle: 7.4

Was able to reproduce it both with jUnit and TestNG, please see the code in the repository below.

Before running tests, make sure neither specific driver locations provided, nor PATH environment variable set for drivers.
Run the tests until you `get java.lang.IllegalStateException: The path to the driver executable...` exception.

### How can we reproduce the issue?

```shell
https://github.com/attila-fazekas/selenium-manager-parallel-run
```


### Relevant log output

```shell
https://github.com/attila-fazekas/selenium-manager-parallel-run/tree/main/logs
```


### Operating System

macOS Mojave

### Selenium version

Java 4.8

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

Chrome  109.0.5414.119, Firefox 108.0.1, Edge 109.0.1518.70

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

ChromeDriver 109.0.5414.74, GeckoDriver 0.32.0, EdgeDriver 109.0.1518.70

### Are you using Selenium Grid?

No
package org.openqa.selenium.manager;
import com.google.common.collect.ImmutableList;
import com.google.common.io.CharStreams;
import org.openqa.selenium.Beta;
import org.openqa.selenium.Platform;
import org.openqa.selenium.WebDriverException;
import java.io.File;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.nio.charset.StandardCharsets;
import java.nio.file.Files;
import java.nio.file.Path;
import java.util.Arrays;
import java.util.logging.Logger;
import static java.nio.file.StandardCopyOption.REPLACE_EXISTING;
import static org.openqa.selenium.Platform.MAC;
import static org.openqa.selenium.Platform.WINDOWS;
/**
 * This implementation is still in beta, and may change.
 *
 * The Selenium-Manager binaries are distributed in a JAR file (org.openqa.selenium:selenium-manager) for
 * the Java binding language. Since these binaries are compressed within these JAR, we need to serialize
 * the proper binary for the current platform (Windows, macOS, or Linux) as an executable file. To
 * implement this we use a singleton pattern, since this way, we have a single instance in the JVM, and we
 * reuse the resulting binary for all the calls to the Selenium Manager singleton during all the Java
 * process lifetime, deleting the binary (stored as a local temporal file) on runtime shutdown.
 */
@Beta