Updated instructions for building on macOS and debugging via intellij (#843)

* Updated instructions for building on macOS and debugging via intellij

* Update docs/src/doc/user-guide/debugging.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* feedback

* Revert theme change

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: falcon4ever

docs/src/doc/assets/img/remote_debug_configuration_godot_dialog.png

@@ -4,6 +4,18 @@ Using the Godot editor:
 
 ![Build button](../assets/img/editor-plugin/build_button.png)
 
+!!! warning
+    On Linux or macOS you may receive an error when trying to build the project from the Godot editor (This can happen if you created your project via the IntelliJ template). 
+    ```shell
+    ERROR: Godot-JVM: Could not create child process: /Users/username/projectname/gradlew 
+    ERROR:  at: execute_with_pipe (drivers/unix/os_unix.cpp:659)
+    ```
+    
+    In such case, open up the terminal and change the permissions of the `gradlew` file to be executable.
+    ```shell
+    chmod +x gradlew
+    ```
+
 Using your IDE:
 
 ![Gradle task](../assets/img/build_ide.png)
@@ -44,4 +56,4 @@ gradlew build -Prelease
 
 Using debug builds is recommended when developing. It adds some sanity checks that are cut off in `release`.  
 
-Release builds are recommended when distributing to retail.
+Release builds are recommended when distributing to retail.

docs/src/doc/assets/img/remote_debug_configuration_godot_menu.png

@@ -12,14 +12,53 @@ If you're still using the JDK installed on your system though, you don't need to
 
 ## Run and attach a Remote Debugger
 
-Run your game with the command-line option `--jvm-debug-port=<port (normally 5005)>` and attach a remote debugger.
+Breakpoint based debugging is available via the remote debugger.
+
+#### 1. Customize Run Instances in Godot
+
+Open up the **Customize Run Instances** dialog from the **Debug** menu in Godot
+
+![remote debug configuration_step_1](../assets/img/remote_debug_configuration_godot_menu.png)
+
+#### 2. Specify the arguments
+
+In the **Main Run Args**, you should specify your commandline options. In the example below we use port `5005` by specifying: `--jvm-debug-port=5005`
 
 !!! info
     If you specify either `--jvm-debug-port` or `--jvm-debug-address` the execution of the game will suspend until you attach a remote debugger. You can configure this behaviour by specifying `--wait-for-debugger=true` or `--wait-for-debugger=false`
 
-Example:  
-![remote debug configuration](../assets/img/remote_debug_configuration.png)
+![remote debug configuration_step_2](../assets/img/remote_debug_configuration_godot_dialog.png)
+
+#### 3. Create a new configuration in IntelliJ
+
+Create a new **Configuration** using **Remote JVM Debug**
+
+![remote debug configuration_step_3](../assets/img/remote_debug_configuration_intellij.png)
+
+#### 4. Setup the new configuration in IntelliJ
+
+Use the same port as you used in step 2, in our case `5005`
+![remote debug configuration_step_4](../assets/img/remote_debug_configuration.png)
+
+#### 5. Set a breakpoint in IntelliJ
+
+![remote debug configuration_step_5](../assets/img/remote_debug_configuration_intellij_breakpoint.png)
+
+#### 6. Launch the game in Godot
+
+Depending on your flags (`--wait-for-debugger`), the game will suspend until you attached the remote debugger from IntelliJ
+
+#### 7. Run the Debug Game configuration
+
+Run the **Debug Game** configuration you made earlier in IntelliJ
+
+![remote debug configuration_step_6](../assets/img/remote_debug_configuration_intellij_configuration.png)
+
+#### 8. Breakpoint
+
+IntelliJ will now automatically pause when the breakpoint is hit
 
+![remote debug configuration_step_7](../assets/img/remote_debug_configuration_intellij_breakpoint_hit.png)
 
 ## Write debug code
 
@@ -32,4 +71,4 @@ Example:
 if (GodotJvmDefinitions.DEBUG) {
     // ...
 }
-```
+```