Describe the bug

When running QuarkusMainTest via maven in the project causes "fresh" dependencies downloads. What is more this dependencies are downloaded not considering the actual pom settings. In my case I have a dependency that is placed in private gcloud artivact registry. I have repository section setup with this artifactregisty. During build it is properly resolved and dependency is downloaded and cashed in my local repo. When test is running it does not check local cache and downloads all dependencies and fails when it encounter the one that is private.

The problem starter happening when upgraded quarkus version from 3.11.3 to 3.12.0.
Commit number that causes this issue: 11e1e86
This bug is caused by changes in WorkspaceLoader after enabling parallel module loading.

Expected behavior

Cashed repository is used and no additional downloads occurs.

Actual behavior

A lot of dependencies are downloaded, pom settings are not considered.

How to Reproduce?

1. Create a project with dependency that is not publicly available
2. Create a QuarkusMainTest that relies on this dependency
3. Run the test
4. Observe it failed due to dependency resolution failure

Output of uname -a or ver

osx arm64

Output of java -version

OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (build 17.0.10+7, mixed mode)

Quarkus version or git rev

3.12.0

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)

Additional information

No response