Handle CircleCI jobs without the "dependencies" property in the workflow notifier.

[filipsobol]

🚀 Summary

Handle CircleCI jobs without the dependencies property in the workflow notifier. The CircleCI API may return job objects without that property, which caused processJobStatuses() to throw. Such jobs are now treated as jobs with no dependencies.

---

📌 Related issues

• Closes https://github.com/ckeditor/ckeditor5-internal/issues/4559

---

💡 Additional information

The fix is a minimal optional-chaining guard (!job.dependencies?.length); the later dependency lookup is already gated behind that check. Added test coverage for jobs with a missing dependencies property.

[pomek]

From the issue DoD's:

Consider adding retry logic to handle CircleCI API instability

Was this considered? And if so, why did you reject implementing it?

[filipsobol]

From the issue DoD's:

Consider adding retry logic to handle CircleCI API instability

Was this considered? And if so, why did you reject implementing it?

Yes, but I generally avoid adding logic for blindly retrying the code because it can mask real issues. It would be overkill here because the fix for the actual root cause was small enough, and such errors are so uncommon.

IMO, retry logic should only be added as a last resort, when the provided code is fundamentally flawed and cannot be fixed or the expense is too great to justify.