Fix job editor switches to the snapshot version when body is changed

[midigofrank]

Description

This PR fixes the bug on the inspector that switches the job editor back to the snapshot version whenever the user types anything in. You can check the issue #2306 for a video on this

Closes #2306
Closes #2308

Validation steps

In order to validate this, we'll need to have a workflow with at least one job in it.
We'll create a manual work order using the job as it is, then later update the job body to have something else.
This way, we'll have a work order with an older version of the job body.

These instructions assume you've done the the above

1. Open up the inspector from the executed step of the work order in the history page
2. The inspector will open up in "snapshot mode". Now toggle to switch to the latest version
3. Notice that the job editor content gets updated to the latest job body.
4. If you try changing the job body, the content gets updated and the editor doesn't switch back to the snapshot version

Pre-submission checklist

• I have performed a self-review of my code.
• I have implemented and tested all related authorization policies. (e.g., :owner, :admin, :editor, :viewer)
• I have updated the changelog.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.72%. Comparing base (be6970f) to head (8946386).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2319      +/-   ##
==========================================
- Coverage   89.73%   89.72%   -0.01%     
==========================================
  Files         298      298              
  Lines       10039    10038       -1     
==========================================
- Hits         9008     9007       -1     
  Misses       1031     1031              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[elias-ba]

@midigofrank this is looking good to me, great job 👏. I left a comment but up to you to handle it or not.

[elias-ba]

Maybe we should remove it in this work, what do you think ?

[midigofrank]

I don't feel confident enough to remove it at this time. I was thinking of removing it as a follow-up when everything is tested and works fine

[christad92]

Loooooveeee eeeeeett!!

Thanks mate!