Fix problems related to dockersand.bat

[Hoikas]

Got a report on discord:

PS D:\dirtsand> ./dockersand build
./dockersand : File D:\dirtsand\dockersand.ps1 cannot be loaded because running scripts is disabled on this system.
For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ ./dockersand build
+ ~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

Assuming that ./dockersand is mapping to dockersand.bat, the default policy might be messing with us. Most all resources online suggest using NoProfile when using helper scripts to launch PowerShell, so let's do it.

[dpogue]

If you are running in a PowerShell prompt then I'm pretty sure ./dockersand is the .ps1 file.

[Hoikas]

If you are running in a PowerShell prompt then I'm pretty sure ./dockersand is the .ps1 file.

Confirmed

PS D:\Plasma\dirtsand> ./dockersand help
dockersand - DIRTSAND for Docker
Available commands:
    attach - attach to the DIRTSAND console
    build - rebuild the DIRTSAND containers from the source and compose files
    restart - restart the DIRTSAND containers
    start - start the DIRTSAND containers
    status - check if the DIRTSAND containers are running
    stop - stop the DIRTSAND containers
PS D:\Plasma\dirtsand> Remove-Item dockersand.bat
PS D:\Plasma\dirtsand> ./dockersand help
dockersand - DIRTSAND for Docker
Available commands:
    attach - attach to the DIRTSAND console
    build - rebuild the DIRTSAND containers from the source and compose files
    restart - restart the DIRTSAND containers
    start - start the DIRTSAND containers
    status - check if the DIRTSAND containers are running
    stop - stop the DIRTSAND containers
PS D:\Plasma\dirtsand> git status
On branch pwsh_noprofile
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        deleted:    dockersand.bat

Upon manually executing dockersand.bat, I found that it didn't even work. I've pushed a fix for that, and I'll push some changes to the README to point toward the command prompt offer real suggestions for execution policy exceptions in PS prompts.