dependencyCheckAggregate Cross Project Resolution Issues (Gradle plugin)

[Fleshgrinder]

Describe the bug
Executing dependencyCheckAggregate with Gradle 7 in a build with multiple projects leads to:

Resolution of the configuration :some-project:some-configuration was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.3.2/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.

Version of dependency-check used

• Gradle Plugin 6.5.0.1
• Gradle 7.3.2

Expected behavior
No warnings are logged.

Additional context
The Gradle team plans to introduce project isolation, rendering the plugin unusable in the future. I think that it would be good to resolve this today, so that there are no surprises tomorrow. That said, today DependencyCheck still works great with Gradle 7, it's just that when you run a build with 20+ subprojects each having x configurations that you are greeted by 100+ lines of warnings by Gradle. Consequently this also means that it is impossible to run a build that has Gradle's warning mode set to fail.

I searched the issues and pull requests, but could not find anything. Apologies if it is a duplicate and my search-fu failed me.