When executing a workflow through a project, output to worklflow/tmp

Users can execute a workflow with the command:

openfn my-workflow

This will load the current project and work out where my-workflow is from there.

When we do this, by default the output path will be my-workflow/output.json . Which is odd because the workflow lives in workflows/my-workflow. It means a messy new diff has been created and its not a nice experience.

It would be nicer to default the output to tmp/output.json, relative to the workflow.yaml file.

What about input paths? If I do -s input.hson should that be relattve to workflow/tmp? cwd? Perhaps if you do ./state.json we'll do it relative to the workspace root, but if you just do state.json we load it from /tmp. Then again its not hard to do -s tmp/input/json.

So what if we say that all input and output paths for a workflow are relative to the workflow yaml? If no path is included we do tmp/state.

Start at the openfn my-workflow command and trace how it resolves workflow.yaml and selects the default output path. Review the existing -s input-path handling, then settle the relative-path rules before changing behavior; done means input and output paths consistently follow the agreed workflow-relative defaults.