Support configuration cache (second attempt)

[MyDogTom]

📌 References

• Issue: Gradle Configuration Cache compatibility #263
• **Related pull-requests:**Support configuration cache #291

🎩 What is the goal?

Ensure that configuration cache works after Gradle daemon is recreated.

How is it being implemented?

• Avoid using global variable because Gradle has no idea about it and cannot recreate when configuration cache is reused. Use explicit task input instead.
• Annotate other task inputs.
• Convert internal "shot" property to function. It's used only once by each task anyway.

How can it be tested?

• ./gradlew debugExecuteScreenshotTests --configuration-cache
• ./gradlew --stop
• ./gradlew debugExecuteScreenshotTests --configuration-cache - should display "Reusing configuration cache."

[pedrovgs]

Thanks for the contribution @MyDogTom I'm wondering if we could automate the checks you mentioned in the PR description to ensure any future change in this plugin will not break this feature.

[MyDogTom]

@pedrovgs I was thinking about enabling configuration cache in the sample project, but this depends on AGP update and can be done only after #292 is merged.
Once sample app has configuration cache enabled, it should be possible to automate the same scenario.

[pedrovgs]

Thanks for the info and your contribution @MyDogTom! I'm merging this PR right now and releasing a new version ASAP 😃