The plugin must be specifically configured for a multi-project setup.

### 🤔 What's the problem you've observed?

I have a multi-project setup where the root is project A and there are two subprojects, B and C.
The projects are configured in Gradle, and the development environment is VS.
For the plugin to correctly read the steps from the feature file in project C, I had to add the following entry to the plugin configuration:

"cucumber.glue": [
"C/src/test/**/*.java",
...
]

### ✨ Do you have a proposal for making it better?

add subproject support to be work with default configuration "src/test/**/*.java"

### 📚 Any additional context?

_No response_

Start by examining the plugin configuration handling and how the default `src/test/**/*.java` pattern is resolved for Gradle projects. Reproduce the root project A with subprojects B and C, then verify that feature steps in project C are discovered without adding a project-specific `cucumber.glue` entry.

Written by the indexing model from the issue text.