Saving a draft revision will remove the node from the queue

Problem/Motivation

When saving a new draft revision of a published node, the node is incorrectly removed from all assigned entityqueues, even though a published version still exists.

Steps to reproduce

1. Create a published node and add it to an entityqueue via the entityqueue_form_widget
2. Create a new draft revision of that node (e.g., by editing it and selecting "Save as Draft")
3. Save the draft
4. Check the entityqueue - the node has been removed

Root Cause

The entityqueue_form_widget_form_node_form_submit() function checks only the current revision's publication status ($node->isPublished()) when deciding whether to remove the node from queues. Since draft revisions are unpublished, this causes the removal logic to treat the entire entity as unpublished and remove it from all queues.

Proposed resolution

Check if any published revision of the node exists in the database before removing it from queues. If a published version exists, only remove from unchecked queues. If no published version exists, remove from all queues.

Remaining tasks

• ✅ File an issue about this project
• ✅ Addition/Change/Update/Fix to this project
• ✅ Testing to ensure no regression
• ➖ Automated unit/functional testing coverage
• ➖ Developer Documentation support on feature change/addition
• ➖ User Guide Documentation support on feature change/addition
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Reviewed by a human
• ❌ Code review by maintainers
• ✅ Full testing and approval
• ✅ Credit contributors
• ✅ Review with the product owner
• ✅ Update Release Notes
• ✅ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• N/A