Cannot run Grails update with WSL2 - Cannot run program...

***What steps will reproduce the issue?***
1\. I have a project cloned to WSL2, this is Grails code. I also have the Grails plugin installed (official, newest version). The project JDK is set to be a JDK available on WSL.
2\. When Intellij imports new modules it tries to do the dependency update, but it fails with the error saying that the program cannot be run since it is not valid Win32 app.
3\. The same error is visible when doing it manually through Tools menu -> Run Grails command
_⚠️ attachment `image1.png` was not included in the export_

***What is the expected result?***
The expected result is that Grails dependencies got refreshed.

***What happens instead?***
I see an error:
_⚠️ attachment `image.png` was not included in the export_
How is it possible that Intellij is supporting WSL and yet, it seems it is not?

*Please attach the [IDE logs](https://intellij-support.jetbrains.com/hc/en-us/articles/207241085) to the issue. You can get them by selecting Collect Logs and Diagnostic Data from the Help menu.*
[idea-logs-20240221-09453910762792122762390627.zip](idea-logs-20240221-09453910762792122762390627.zip)
IntelliJ IDEA 2022.2.5 (Ultimate Edition)
Build #IU-222.4554.10, built on March 15, 2023
Runtime version: 17.0.6+7-b469.82 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 8192M
Cores: 20
Non-Bundled Plugins:
com.haulmont.rcb (2023.1.5-222)
org.intellij.grails (222.4459.16)

Kotlin: 222-1.7.10-release-334-IJ4554.10

---

*2 attachment(s) referenced here (`image1.png`, `image.png`) are not part of the CSV export.*
*Imported from [IDEA-346869](https://youtrack.jetbrains.com/issue/IDEA-346869) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Start with the Tools menu's Run Grails command and the dependency update triggered when IntelliJ imports modules. Review the provided IDE logs and reproduce the failure with the Grails project cloned in WSL2 and its WSL JDK configured. Done means Grails dependencies refresh without the invalid Win32 application error.

Written by the indexing model from the issue text.