Extend usages to any project

Hi, I was trying to figure out https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/issues/630 with this plugin, but I noticed that this plugin starts with:

pluginManager.withPlugin("java-gradle-plugin") {

which means I can't just apply it to my project to scan all build.gradle/build.gradle.kts files too.

Would it be possible to extend the scanning to those files? It's great for authoring plugins, but for discovering issues in potentially huge projects, where multiple third party plugins are applied (which don't use this plugin), it cannot be used :(

I ended up applying to includeBuild("gradle/plugins") as a fallback, at least that covers the majority of the Gradle scripts. I have a feeling this should be called out in the README.md too.

Also in a similar vein it would be nice to be able to analyze all the buildEnvironment for these. It only recognized usages in my own .class files, but I suspect there are others from third party plugins too that I'm not knowing about.

Start at the pluginManager.withPlugin("java-gradle-plugin") entry point and review how scanning is limited to plugin projects. Compare that behavior with the requested build.gradle/build.gradle.kts and third-party buildEnvironment coverage, then inspect README.md for the current documented scope. Done means the requested project-wide usage is supported or its scope is clearly documented.