Merge

Updates

1. This is what matters the most in this update; In our last releases, DAws was capable of spawning working batch/bash CGI Shells which was pretty good but these CGI Shells were independent; they had nothing to do with DAws, so, if `system`, `passthru`, `exec`, `shell_exec`, `popen` and `proc_open` were all disabled then the `Process Manager` and Most of the `Eval` forms would completely fail even though our CGI Shell is there which wasn't enough, so I've decided to Merge it completely with DAws. What I'm trying to say is that, now, DAws fully communicates with the CGI Shell to do everything needed. 2. When you login/a new session is created, DAws will automatically drop these CGI shells and everything related to them in the `writeable/readable` directory that was found by the `Directory Roaming` function and it will also test them out to check if they're working, and if they are then DAws will start communicating with them completely. 3. The Bash CGI Shell has been updated, now, it only receives base64 encoded `get` data since that was extremely needed because WAFs were easily blocking the CGI Shell. I know that base64 isn't enough but we will be implementing DAws's encoding system into the CGI Shell soon. When it comes to the Batch CGI Shell, it's not working properly now because we didn't finish updating it yet but it should done within 24 hours. 4. We added a new function called `url_get_content` which uses Curl to get the output of the CGI Shells along with `file_get_contents` and that is because `file_get_contents` won't work if `allow_url_fopen` was disabled. 5. The feature that checks the `Free Memory` on windows has been fixed. 6. Thanks to asm-99 who reported the bug, the `Directory Roaming` function has been updated.

Thank you all for supporting DAws,
dotcppfile.