Unsaved changes indicator

[doc-han]

Description

This PR shows a red dot indicator on the save button when there are unsaved changes in a workflow.

Closes #3682

Validation steps

1. Open a workflow
2. Make some changes to a job/edge
3. Do you see a red dot showing that some unsaved changes exist? we expect a yes

If you're seeing a red dot right upon entering a workflow, it means there already exist unsaved changes(between what's in the DB and what's on ydoc).

Additional notes for the reviewer

1. (Is there anything else the reviewer should know or look out for?)

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our Responsible AI Policy

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.
• I have ticked a box in "AI usage" in this PR

[codecov]

Codecov Report

❌ Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.32%. Comparing base (e46806e) to head (99c0c8d).

Files with missing lines	Patch %	Lines
lib/lightning_web/channels/workflow_channel.ex	71.42%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4289      +/-   ##
==========================================
- Coverage   89.37%   89.32%   -0.05%     
==========================================
  Files         425      425              
  Lines       19940    19941       +1     
==========================================
- Hits        17821    17812       -9     
- Misses       2119     2129      +10     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[taylordowns2000]

noting project_credential_id from our call! ping when ready to test again please :-)

[taylordowns2000]

works great @doc-han . i've requested a review from @stuartc since he worked on this also before the break.

two things (not blocking for me):

1. see comment on the hard-coded expected structure. is there another way?
2. check out the issue (and comment) here about warning on unsaved changes... i think it would be really nice to finally tell users "hey, you're about to navigate away with unsaved stuff" and I wonder if this new function allows us to do that?

[lmac-1]

Most of my review comments are low priority / nice-to-haves and shouldn't block merging.

But I noticed that "Allow console.log() usage" (workflow.enable_job_logs) and "Max concurrency" (workflow.concurrency) don't trigger the unsaved changes dot. This should be addressed before merging.

[doc-han]

Thanks for the reviews @lmac-1 @stuartc. All change requests resolved. Please take a look once again.