[ZEPPELIN-6565] Re-enter Angular zone for React remote callbacks

[miinhho]

What is this PR for?

This PR fixes ReactMountDirective so callbacks invoked by a mounted React remote re-enter the Angular zone before calling back into the Angular host.

ReactMountDirective mounts and updates React remotes inside ngZone.runOutsideAngular(). The directive already used ngZone.run() for errors reported through its own reportError() path, but props were passed to the remote unchanged. As a result, a remote such as the React paragraph footer could call props.onError() directly from outside the Angular zone.

For an Angular OnPush host component, that can mark the component dirty without scheduling change detection, delaying the fallback UI until some later zone-scheduled work occurs.

This change wraps host callbacks as props enter ReactMountDirective, while keeping the original props (latestRawProps) available for directive-internal error reporting. The wrapped props (latestProps) are passed to both mount() and update(), so React remote callbacks consistently run through the Angular zone boundary.

What type of PR is it?

Bug Fix

What is the Jira issue?

• https://issues.apache.org/jira/browse/ZEPPELIN-6565

How should this be tested?

Run the shell unit tests:

cd zeppelin-web-angular
npm run test:shell

Questions:

• Does the license files need to update? No
• Is there breaking changes for older versions? No
• Does this needs documentation? No

[voidmatcha]

LGTM 👍

Future host callbacks should follow the same zone-handling pattern.

[tbonelee]

LGTM, approving.

Verified on a running dev server: Zone.current was <root> inside onError every run, so the diagnosis holds and the directive is the right place to wrap it.

One correction on the rationale, not on the patch. The issue, and the existing reportError comment, both say a markForCheck() from outside the zone has "nothing to flush it". That is not true on Angular 18+, where hybrid scheduling schedules a tick for exactly that case: the fallback rendered 1 to 4 ms after onError. The fix still stands, just for a different reason, that async work a host handler starts stays untracked by NgZone without ngZone.run().

Nothing to do on your side. I will fix that comment, since it is mine (from 52a638e), and note the correction on the issue.

[tbonelee]

Merged into master