`packageJvmWindowsApp` doesn't work with `org.gradle.configuration-cache=true`

And people need to comment them in the `gradle.properties`:

```
#org.gradle.configuration-cache=true
#org.gradle.configuration-cache.problems=warn
```

We will need to test in e2e tests to avoid regressions.

`packageJvmLinuxApp`, `packageJvmMacosApp` and `packageJvmWindowsApp`.

Start by enabling the configuration-cache settings in gradle.properties and reproducing the failure with packageJvmLinuxApp, packageJvmMacosApp, and packageJvmWindowsApp. Inspect the existing end-to-end tests and extend them so all three packaging tasks work with configuration-cache enabled without regressions.

Written by the indexing model from the issue text.