File path support for jobs in project import/export

Description

When using a file path for job body in project.yaml As instructed here in versions portability proposal v4, The job editor on lightning fails to render the actual job code, instead it displays the literal file path.

Steps to Reproduce

1. Clone OpenFn/demo-openhie project locally
2. Open project.yml and edit Transform-data-to-FHIR-standard body path to file://./jobs/expression.js
3. Save and commit your changes
4. Login on demo.openfn.org as demo users demo@openfn.org
5. On dashboard open OpenHIE Workflow
6. Click on Transform-data-to-FHIR-standard step to open the job editor
7. Observe that the editor displays the file path instead of the job code

Expected Behavior

The Lightning Job Editor should accurately interpret the specified file path in the project.yaml file, rendering and displaying the corresponding job code.

Screenshots

https://github.com/OpenFn/Lightning/assets/6592749/02badd41-2436-46da-b30b-575b6d4511dc

Additional information

• We need to know where jobs are kept so that the export builds the project.yaml properly
• We need to know if any changes needs to happen on https://github.com/OpenFn/kit/tree/main/packages/deploy

Start by tracing project import/export handling in the kit repository, especially the packages/deploy area mentioned in the issue, and compare it with the project.yaml file path example and jobs/expression.js fixture. Verify how the file:// path reaches the job editor. Done means the editor renders the referenced job code and project export writes the appropriate path.