Run AsyncResource completions on EDT in InternalCallback

[shai-almog]

Motivation

• Ensure that AsyncResource completion, error and cancel handlers are executed on the UI thread to avoid threading issues.
• Prevent race conditions where a request may be completed/cancelled multiple times by double-checking isDone.
• Improve stability of fingerprint/back-end callbacks that interact with UI or UI-tied state.

Description

• Wrap req.complete, req.error, and req.cancel calls in Display.getInstance().callSerially(...) in InternalCallback so they run on the EDT.
• Retain an outer !req.isDone() guard and add an inner !req.isDone() check inside the runnable to avoid duplicate terminal actions.
• Apply the change to requestSuccess, requestError, requestKeyRevokedError, and requestComplete methods.

Testing

• Ran the project's automated test suite and build, and the tests completed successfully.
• Verified that the modified callback paths execute without throwing threading-related exceptions in automated runs.
• No automated tests failed as a result of these changes.

---

Codex Task

[shai-almog]

@shannah can you please review?
This is supposed to address an issue discussed in crisp in which Dialogs won't show on iOS in the callback code because it thinks the app is minimized.

[Copilot]

Pull request overview

This PR updates InternalCallback in the fingerprint module to ensure AsyncResource terminal handlers (complete/error/cancel) execute on Codename One’s EDT, reducing UI-threading hazards in native callback paths.

Changes:

• Wrap req.complete(...), req.error(...), and req.cancel(...) in Display.getInstance().callSerially(...) so terminal events run on the EDT.
• Add an inner !req.isDone() guard inside the EDT runnable to prevent duplicate terminal actions when multiple callbacks race.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.