Fix OHOS deadlock when release() and OnSurfaceDestroyedCB race for the same mutex.

[CodeJhF]

Problem

Fixes #3438

On OHOS platform, a deadlock can occur when release() and OnSurfaceDestroyedCB race for the same mutex in JPAGView / JPAGImageView:

1. Thread A calls release() → acquires locker → animator->cancel() may wait for the animation thread
2. Thread B (XComponent callback thread) calls OnSurfaceDestroyedCB → finds listener in XComponentListeners → calls onSurfaceDestroyed() → tries to acquire locker → deadlock

Fix

Call XComponentHandler::RemoveListener(id) at the very beginning of release(), before acquiring the mutex. This disconnects the view from XComponent callbacks so the callback thread can no longer reach the mutex, eliminating the deadlock.

The double-remove is safe: RemoveListener returns false harmlessly if the key is already gone (the napi_wrap finalizer also calls RemoveListener later during GC).

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.10%. Comparing base (1151b28) to head (53cdfde).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3522      +/-   ##
==========================================
+ Coverage   81.06%   81.10%   +0.04%     
==========================================
  Files         626      626              
  Lines       71226    71226              
  Branches    20826    20826              
==========================================
+ Hits        57737    57770      +33     
+ Misses       9352     9344       -8     
+ Partials     4137     4112      -25     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.