IssueTracker

If an included build of a composite Gradle build does not have a settings file, version catalogs are not collected properly. It breaks the navigation from a build script to a version catalog. This happens because in the case of settings file absence, BuildModelContext class searches for settings files in upper directories. This behavior is applicable for subprojects but not for included builds

STEPS TO REPRODUCE:
1. Open attached project "groovy-test-composite"
2. Go to groovy-test-composite > curious dragon > build.gradle
3. There are 2 dependencies with "Unrecognized dependency notation" warning and not working navigation to .toml file

This problem is also described and resolved in https://youtrack.jetbrains.com/issue/IDEA-361677