over eager dangerous commands

[michaelneale]

    dangerous_patterns = [
        # Commands that are generally unsafe
        r"\brm\b",  # rm command
        r"\bgit\s+push\b",  # git push command
        r"\bsudo\b",  # sudo command
        r"\bmv\b",  # mv command
        r"\bchmod\b",  # chmod command
        r"\bchown\b",  # chown command
        r"\bmkfs\b",  # mkfs command
        r"\bsystemctl\b",  # systemctl command
        r"\breboot\b",  # reboot command
        r"\bshutdown\b",  # shutdown command
        # Target files that are unsafe
        

rm and mv may be ok in many cases as the user has specifically asked goose to do some work and it can be a little over eager. Could we make it smarter:

• have a global "go ahead" say when running "goose run"
• if it is running commands in current dir and there file isn't unstaged (ie git has it backed up) then it may be ok to go ahead within that context of current project?

[michaelneale]

@baxen it may be time to bring back the accelerator check: only in this case use it to decide based on system if it should continue as lower risk than on face of it?