Migrate plugin to use Gradle's task configuration avoidance APIs

Gradle recommends to use the task configuration avoidance APIs whenever tasks are created in custom plugins.

> In a nutshell, the API allows builds to avoid the cost of creating and configuring tasks during Gradle’s configuration phase when those tasks will never be executed. For example, when running a compile task, other unrelated tasks, like code quality, testing and publishing tasks, will not be executed, so any time spent creating and configuring those tasks is unnecessary. The configuration avoidance API avoids configuring tasks if they will not needed during the course of a build, which can have a significant impact on total configuration time.

See more info [here](https://docs.gradle.org/current/userguide/task_configuration_avoidance.html).

Please let me know if you are interested in getting this issue resolved. I would be very happy to contribute.

Thanks in advance!

Read the linked Gradle task configuration avoidance guidance, then inspect the plugin's task creation sites. Migrate the custom plugin to the recommended APIs and verify that existing plugin behavior remains intact; the issue names no files or tests, so the relevant entry points must first be located.

Written by the indexing model from the issue text.