The Kotlin DSL GroovyBuilder should support invoking methods taking Closure with arguments

[eskatos]

One Gradle API, for defining dependency management component selection rules, makes use of Closure taking configuration methods that takes a variable number of arguments.

See #6607

This API will get fixed but community plugins may rely on similar constructs.

withGroovyBuilder {} or (delegate)closureOf() and KotlinClosure* don't help much because the former doesn't allow access to the list of the closure parameters and the latter don't support more than 2 arguments where that api requires 3.

This issue is about enhancing the Groovy interoperability APIs to support that usecase.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.