Support configurable presentation of project names in test runner

When working with vscode workspaces having multiple folders/projects, it would be useful to have more options on how the project names are presented in the test runner. In a complex setup, you might have tens of folders/projects open as the same time with a mixture of gradle and maven projects. Organizations might have repository naming conventions resulting in lengthy names, which makes it challenging to navigate with the current behaviour in the test runner. In addition, maven and gradle project are currently presented differently.

Gradle project without project name defined in settings.gradle:
"project directory name" (might be lengthy in itself)

Gradle project with project name defined in settings.gradle:
"root project name-project directory name" (results in even lenghtier names)

Maven project:
"project artifact id"

Proposed behaviour:

Make it configurable which value should be presented.

• vscode workspace file "folder.name"
• file system folder name (typically same as the repository name)
• maven project name or artifactId / gradle rootProjectName
• a combination of the above

It would be especially nice to be able to choose the vscode workspace folder name, which allows for setting short context specific names.

An alternative is to introduce a default order of selection

1. vscode workspace folder name if defined
2. maven project name / gradle root project name if defined
3. file system folder name

The maven plugin has a similar concept for the format of project node names.

Beginne damit nachzuverfolgen, wie der VS Code-Test-Runner derzeit Maven- und Gradle-Projektnamen darstellt, wobei die vorgeschlagenen Quellen workspace-folder, filesystem-folder und project-name als Anforderungen verwendet werden. Lege die konfigurierbare Auswahl oder Reihenfolge fest und überprüfe anschließend, dass Projekte mit unterschiedlichen Benennungsquellen den ausgewählten Wert konsistent anzeigen.