A modern programming language that makes developers happier.

kotlinlang

What does validate gradle wrapper do? Because I get errors on it like 50% of the time. See :thread:

```Run gradle/actions/wrapper-validation@v3
Error: Multiple errors returned
Error: Error 0: connect ETIMEDOUT 104.16.73.101:443
Error: connect ETIMEDOUT 104.16.73.101:443
    at createConnectionError (node:net:1652:14)
    at Timeout.internalConnectMultipleTimeout (node:net:1711:38)
    at listOnTimeout (node:internal/timers:583:11)
    at process.processTimers (node:internal/timers:519:7)
Error: Error 1: connect ENETUNREACH 2606:4700::6810:4965:443 - Local (:::0)
Error: connect ENETUNREACH 2606:4700::6810:4965:443 - Local (:::0)
    at internalConnectMultiple (node:net:1186:16)
    at Timeout.internalConnectMultipleTimeout (node:net:1716:5)
    at listOnTimeout (node:internal/timers:583:11)
    at process.processTimers (node:internal/timers:519:7)
Error: Error 2: connect ETIMEDOUT 104.16.72.101:443
Error: connect ETIMEDOUT 104.16.72.101:443
    at createConnectionError (node:net:1652:14)
    at Timeout.internalConnectMultipleTimeout (node:net:1711:38)
    at listOnTimeout (node:internal/timers:583:11)
    at process.processTimers (node:internal/timers:519:7)
Error: Error 3: connect ENETUNREACH 2606:4700::6810:4865:443 - Local (:::0)
Error: connect ENETUNREACH 2606:4700::6810:4865:443 - Local (:::0)
    at internalConnectMultiple (node:net:1186:16)
    at Timeout.internalConnectMultipleTimeout (node:net:1716:5)
    at listOnTimeout (node:internal/timers:583:11)
    at process.processTimers (node:internal/timers:519:7)```

<https://github.com/gradle/actions/tree/main/wrapper-validation>

Given the note, we can just remove the explicit wrapper validation step <https://github.com/kotest/kotest/blob/8d26ff395f0e869290f4aeb0015920dac826c93b/.github/workflows/run-gradle.yml#L58>

&gt; Note
&gt; Starting with v4 the `setup-gradle` action will automatically <https://github.com/gradle/actions/blob/main/docs/setup-gradle.md#gradle-wrapper-validation|perform wrapper validation> on each execution.
&gt; If you are using `setup-gradle` in your workflows, it is unlikely that you will need to use the `wrapper-validation` action.

ok cool I will remove since we use  setup-gradle v4

Made a mini PR for doing so as well, if you wanna get it out asap, <https://github.com/kotest/kotest/pull/4917>