Track webhook_reply and cron_cursor_job in workflow.yaml

The new sync API needs to track webhook_reply and cron_cursor_job in the workflow.yaml file somehow, so that users can see and edit those values.

They're currently tracked in project.yaml under the .openfn key. So they're there - but users have no way to edit them locally.

Now this might not be very important. Locally the trigger is ignored -the CLI does nothing for webhooks or cron triggers, and has none of the app logic.

While this issue is open, users cannot locally edit and sync those values. Since they're not used locally this might not be important.

What about GH sync? If I make a change in project A and push to project B, will those changes be manifest? I don't think so - I can't edit the project.yaml and see a change. So sync on these values is also blocked (for v2)

Finally, we need to consider whether the version algorithm needs updating to reflect these values. A v2 sync will only happen if changes to these values affects the version hash. On the other hand it might cause false positives if the webhook reply changes in the app, and the CLI recognises a change (or even a divergence), but on pulling there is no difference.

Honestly probably the best thing to do is add these values to the version hash and pull them into workflow.yaml. Then everything is clean and consisent.

Start by tracing how workflow.yaml and project.yaml currently represent the .openfn values, then find the sync and version-hash entry points. The change should make webhook_reply and cron_cursor_job editable in workflow.yaml and ensure relevant changes are represented during sync and versioning; the issue does not name specific tests.