Would it be possible to allow using @variables@ in workingDir of RunContainerStep?

The image name, container arguments, environment variables, and volume mount paths already allow them, with workingDir seemingly the only one left out.

For example, I want to set the working directory to match my volume target path, however the latter uses a variable and now the config is not so elegant or future-proof (e.g. project name changes):

- !RunContainerStep
  name: Run cargo test
  image: rust:latest
  workingDir: '/hardcoded-project-name' # needs to match @project_name@
  args: cargo test
  volumeMounts:
    - sourcePath: '@project_path@/'
      targetPath: '/@project_name@'
  useTTY: false
  condition: ALL_PREVIOUS_STEPS_WERE_SUCCESSFUL