Add `dir:` option for per-command working directory

[ocean]

Summary

Add support for a dir: option in command definitions to allow individual commands to run from a specific working directory, rather than always running from the directory containing the .ahoy.yml file.

This would of course be a backwards compatibility breaking feature, so would have to be part of the schema updates for Ahoy v3.

Current Behavior

Currently, all Ahoy commands execute from the directory containing the .ahoy.yml file (AhoyConf.srcDir). This is hardcoded in the command execution logic:

command := exec.Command(cmdItems[0], cmdItems[1:]...)
command.Dir = AhoyConf.srcDir  // Always uses .ahoy.yml directory

To change directories, users must handle it within the command script:

commands:
  example:
    cmd: |
      cd /some/other/directory
      echo "Now in $(pwd)"

Proposed Feature

Add an optional dir: field to command definitions that specifies the working directory for that command:

ahoyapi: v2
commands:
  frontend-build:
    usage: Build frontend assets
    dir: ./frontend
    cmd: npm run build
    
  backend-test:
    usage: Run backend tests  
    dir: ./api
    cmd: composer test
    
  root-command:
    usage: Command that runs from project root
    # No dir specified - uses default (.ahoy.yml directory)
    cmd: echo "Running from $(pwd)"

[hanoii]

I would go one step further and allow the command to run from the current dir, but related to the root, so this can still be run related to root of ahoy config anywhere, i.e. /root/dir1 will run it from ./dir1 and /root/dir2 will run it from ./dir2

[hanoii]

Maybe also (or instead) add an AHOY_CWD environment variable that's the relative dir for the ahoy.yml file that we can use on the scripts?

[tobyharperdewr]

An AHOY_CWD environment variable as described by @hanoii above would be particularly useful for us.

We want to be able to go in to a theme directory and run something like ahoy npm run build to do handle package installation and theme compilation within the docker container without hard-coding the path in to the ahoy command.

The relative path from the .ahoy.yml will be the same relative path from the WORKDIR in docker so I could just combine the two and make the ahoy commands run in the same directory within the container.