[EasyDoctrine] Clear deferred entity events on flush exceptions

[zeromodule]

Q	A
Bug fix?	yes
New feature?	no
BC breaks?	no
Deprecations?	no
Tests pass?	yes

This change prevents deferred entity events from surviving a failed Doctrine flush().
Without it, long-running workers could dispatch stale events from a previous failed message during a later successful flush(). The fix ensures deferred state is cleared on flush() exceptions.

[eonx-space-to-github-reviews]

Code Review in Space: https://space.prod.v1.tools.eonx.com/p/support/reviews/188/timeline

[akl-95]

Great job on the code review. ✅ Code approved!

Secure code in this PR has been written to best practice standards and covers the following as a minimum. Please ticket if coded this way (also tick if not relevant to this code change):

• Protect from Injection attacks
• Protect data with proper input validation, and protect against buffer overflows, pointers/shared data
• Protect with appropriate encryption and cryptography (E.g. Appropriate hashing, symmetric encryption used, ciphers) if applicable
• Protect against XSS and CSRF
• Ensure that pages, data access etc, are written with appropriate access control authorisation and authentication requirements
• Ensure all important errors and business logic cases are handled
• Ensure forwards and redirects are handled
• Ensure no sensitive data is exposed and appropriate logging in place as required

See procedure for more details: PROC-010 Secure Coding Practices