Temporarily disable configuration cache

[mvicsokolova]

With enabled configuration cache, atomicfu:publish started to fail with the following error:

Invocation of 'Task.project' by task ':atomicfu:cinteropInteropAndroidNativeArm32' at execution time is unsupported.
Invocation of 'Task.project' by task ':atomicfu:cinteropTestInteropAndroidNativeArm32' at execution time is unsupported.
Invocation of 'Task.project' by task ':atomicfu:cinteropInteropAndroidNativeArm64' at execution time is unsupported.
Invocation of 'Task.project' by task ':atomicfu:cinteropTestInteropAndroidNativeArm64' at execution time is unsupported.
Invocation of 'Task.project' by task ':atomicfu:cinteropInteropAndroidNativeX64' at execution time is unsupported.

I could not reproduce this locally, but here is the Windows deploy build and the gradle scan of this build.

Seems (according to the scan), that the problem may be caused by the access to the project during execution from org.jetbrains.kotlin.gradle.tasks.CInteropProcess#toGist() which is incompatible with configuration caches and causes this problem.

So, for now I'll disable configuration cache in the project, so that the release could be published.

[mvicsokolova]

@dkrasnoff could you please take a look at this problem 🙏
This only reproduced at deploy and was not discovered during review :(

[dkrasnoff]

This is a really nasty problem because, as I understand, org.JetBrains.kotlin.gradle.tasks.CInteropProcess#toGist() just hides the real problem.
I could not reproduce it locally as well, even on a Windows machine.

[dkrasnoff]

Yeah, as I thought the problem is not in the KGP and CInteropProcess, but they are hiding the real problem under false-positive error messages.
The real problem is in credential block in publishing, which is unsupported by Configuration Cache now