Update IntelliJ setup instructions with Gradle workaround

[koppor]

I had issues on a Linux machine. Here a tested workaround.

Steps to test

Setup development environment on Debian 12.

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

[subhramit]

Are we sure the community edition doesn't have this issue?

[subhramit]

Suggested change

	2. Move the file into your JabRef code
	2. Move the file to your JabRef project directory

[Siedlerchr]

Have you tried to increse java memory heap size in intellij?
Did you import as gradle project after cloning?

[subhramit]

Suggested change

	4. Wait several minutes until command completes.
	On an Intel(R) Core(TM) i5-1350 (16 GB RAM), it took more than 15 minutes.
	4. Wait until the command execution completes.
	On an Intel(R) Core(TM) i5-1350 (16 GB RAM), it takes more than 15 minutes.

[subhramit]

Suggested change

	When the command line hangs at `:jablib:processResources`, you need to keep waiting there.
	The command line may appear to hang at `:jablib:processResources`, you still need to keep waiting.

[subhramit]

Suggested change

	> This is a workaround for following error:
	> The above is a workaround for following error: