Currently the piper binary is downloaded to the fixed location ${process.cwd()}/${version}/${piperBinaryName} as seen here.
This causes problems when using this action in combination with act to run a piper-step locally.
Please allow for an alternative path configuration input for the action.