[24.1] Allow running and editing workflows for specific versions

[ahmedhamidawan]

This passes the version prop to the routes for editing and running workflows and also to the InvokeWorkflowPayload, so that users can run specific versions of workflows.

Fixes #18367

workflow_run_edit_for_version.mp4
Here, the user opens the run form for the latest version of the workflow (default), and then they switch to the older version (with a different name) and the run form loads with the correct (older) order of steps.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[mvdbeek]

I think I would have preferred if we passed the workflow_id (and not the stored_workflow_id as we do currently) and the ?instance=true parameter instead. It's a bit unfortunate that I named our internal workflow checkpoints version when I added this. The version just corresponds to the number of workflows attached to a stored workflow, so if you import or copy a workflow that number is reset. This might be a little confusing.