Enable Gradle's configuration cache by default

[3flex]

Gradle 7.4 introduces a feature to declare that individual tasks are incompatible with the configuration cache, allowing the feature to be enabled by default while skipping caching when there are tasks in the task graph that don't support it.

More information available in "Disable configuration caching when incompatible tasks are executed" section of the release notes: https://docs.gradle.org/7.4/release-notes.html#config-cache

This PR enables the configuration cache while declaring tasks known to be incompatible with it. Note that there may be some additional tasks that are discovered to be incompatible in future, so this config might need tweaking.

[3flex]

I've updated the label to "housekeeping" since I thought the yellow labels, including "gradle", related to the named subprojects? This doesn't change behaviour of the detekt Gradle plugin at all, just the detekt build itself.

Happy to switch back though if that makes sense when it comes to generating release notes.

[codecov]

Codecov Report

Merging #4576 (466a1ae) into main (1cc61fc) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #4576   +/-   ##
=========================================
  Coverage     84.45%   84.45%           
  Complexity     3330     3330           
=========================================
  Files           479      479           
  Lines         11143    11143           
  Branches       2040     2040           
=========================================
  Hits           9411     9411           
  Misses          699      699           
  Partials       1033     1033           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1cc61fc...466a1ae. Read the comment docs.

[cortinico]

I've updated the label to "housekeeping" since I thought the yellow labels, including "gradle", related to the named subprojects? This doesn't change behaviour of the detekt Gradle plugin at all, just the detekt build itself.

Yup that's better. I've initially added gradle as I expected some changes on some of our tasks. Give that there are none, it's safe to move to housekeeping