Dependency with scope test in gradle falls into the main classpath

[provide a description of the issue]

Environment

• Operating System: MacOs
• JDK version: 17
• Visual Studio Code version: 1.93.1
• Java extension version: v1.34.0

Steps To Reproduce

The gradle project. If there is a dependency on another module in a multi-module project with scope test, then this dependency falls into the main classpath.

Current Result

In build.gradle.kts

  testImplementation(project(":backend:core:model"))
  testImplementation(project(":backend:core:ports"))

In .classpath of this module

	<classpathentry kind="src" path="/ports">
		<attributes>
			<attribute name="gradle.buildServer" value="true"/>
		</attributes>
	</classpathentry>
		<classpathentry kind="src" path="/model">
		<attributes>
			<attribute name="gradle.buildServer" value="true"/>
		</attributes>
	</classpathentry>

Expected Result

In .classpath of this module

	<classpathentry kind="src" path="/ports">
		<attributes>
			<attribute name="test" value="true"/>
			<attribute name="gradle.buildServer" value="true"/>
		</attributes>
	</classpathentry>
		<classpathentry kind="src" path="/model">
		<attributes>
			<attribute name="test" value="true"/>
			<attribute name="gradle.buildServer" value="true"/>
		</attributes>
	</classpathentry>

Additional Informations

Start with the multi-module Gradle project and inspect build.gradle.kts alongside the generated .classpath entries. Reproduce the testImplementation dependency behavior, then verify that affected source entries receive the test=true attribute while retaining gradle.buildServer=true.