If no settings file is found, Gradle will assume the project could be a
subproject and will scan any containing directories for a
settings.gradle. This can cause issues if such a file exists, which can
happen when using a composite build to set up a local development
workspace.