This graph view utilizes the same workflow editor canvas, and instead of showing step details on each step node, it shows the job states for the steps. Clicking on a step expands the details for the invocation step.

The `useInvocationGraph` composable loads the graph based on the original workflow id and invocation object; and the step info is loaded via the `step_jobs_summary` api route.

Also, return a correctly encoded database id field in `step_jobs_summary` api.

This allows users to directly go back and forth between dedicated full-center-panel invocation summaries and the invocations list.

Added a mock implementation for the store to detect fetches and use those to check if invocation or job states are terminal

Otherwise, seleniums would fail for:
```
Timeout waiting on CSS selector [[node-label='...'] [input-name='...'] + .delete-terminal-button] to become clickable.
```

Otherwise, this selenium fails:
`FAILED lib/galaxy_test/selenium/test_workflow_invocation_details.py::TestWorkflowInvocationDetails::test_job_details - selenium.common.exceptions.TimeoutException: Message: Timeout waiting on CSS selector [[data-step="1"] .step-title] to become visible.`
because even if you change tab from Summary to Details, the content is still in the template and the steps in the Summary conflicts with the steps in the Details tab; and are hence not detected in the selenium.

Scroll to activeId when clicked (on mounted, also expand first step that has a failed (`error`) state

Also removes the redundant prop as the value can be local to `WorkflowInvocationSteps`

Without this, the latest version (with potential missing steps from the version that was run) is used to create the graph, and therefore, due to potential mismatch between versions, the graph is incorrect.

...i.e.: the `InvocationsList` for an individual workflow, which doesn't have the workflow name.

If there isn't an errored step, still toggle/expand the last step in the workflow invocation.

By always showing the card at the bottom, with instructions on how to view a job.

This is to make the multiple scrollbars in `WorkflowInvocationOverview` to be clickable (one for the Steps and one for the whole tab)

Also, change the `href` for multiview in this view to a <router-link> (to prevent reload).

Also, do not show a separate input steps section if there is only one input step.

… steps if graph is collapsed, by removing the max-height

Co-authored-by: Laila Los <[email protected]>

Co-authored-by: Laila Los <[email protected]>