fix: [DHIS2-21741] Failed event deletion is not rolled back in the UI

[henrikmv]

DHIS2-21741

Simplifies the delete-event rollback mechanism in DeleteActionModal by replacing the React Query cache lookup with a direct prop.

The delete removes the event from Redux, but the rollback previously read the event data from a separate React Query cache. That cache can be stale, and newly created in-session events are not always present there, which meant rollback could be skipped on delete failure.

Previously, on mutation start the component reconstructed a query key from teiId, programId, and enrollmentId, then dug into the cached enrollment data to find the event for rollback. Now, the already-rendered eventDetails object from EventRow is passed in as a prop and used directly:

- queryClient.getQueryData(key)
-   ?.enrollments
-   ?.flatMap(...)
-   ?.find(e => e.event === eventId)
+ const eventToRollbackOnFail = eventDetails;

This ensures the event is always available for rollback and restored on failure, including newly created in-session events.

This also removes the useQueryClient hook, the ReactQueryAppNamespace import, and three individual ID props in favor of a single typed eventDetails: ApiEnrollmentEvent prop.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🚀 Deployed on https://deploy-preview-4636.capture.netlify.dhis2.org

[simonadomnisoru]

Nice!

[linadhis2]

LGTM from QA perspective.

[dhis2-bot]

🎉 This PR is included in version 106.6.2 🎉

The release is available on:

• AppHub release
• v106.6.2
• GitHub release

Your semantic-release bot 📦🚀