[24.1] Optimize useInvocationGraph for Invocation view

[ahmedhamidawan]

This ensures the graph is only loaded onto the editor once (initially). After that, we update the steps ref only when the step_jobs_summary changes. Only steps that have their jobs summary changed are updated as well.

Fixes #18660

Now, once the step_jobs_summary fetch every 3 seconds returns something different from last time, we look to update the individual steps (we do not load the editor again, we just update properties for the step such as .state or .jobs etc. for steps that had those values change). This seems to optimize it greatly and there is significantly lower lag or performance hit.

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.

[ElectronicBlueberry]

This is a great improvement, thank you!
Test failure is unrelated (test fails in unrelated PRs as well)