fix(core): skip nested tick from onMicrotaskEmpty while tick is running - #70985

…ning

A zone-based app that calls `ApplicationRef.tick()` from outside the Angular
zone can report a spurious NG0101 ("ApplicationRef.tick is called
recursively"). Running work outside the zone and ticking manually is a normal
performance pattern, so the app is correct. In production the error carries no
message and the stack is almost entirely zone.js frames, which makes it
impossible to trace back to the real caller.

Angular enters the Angular zone by itself during such a tick. Effects remember
the zone they were created in, so both the root effect scheduler and
`runEffectsInView` use `zone.run()` to run them. Leaving that `zone.run()`
drops the nesting count back to zero, because the tick started outside the
zone. `checkStable` then emits `onMicrotaskEmpty` synchronously, in the middle
of the running tick.

The zone scheduler's guard for this only checked the zoneless scheduler's
`runningTick` flag. That flag is false for an explicit tick, so the handler
started a nested `_tick()`, which threw. The guard was added in angular#55290 and its
comment already describes the mechanism, but it only covered ticks the
scheduler itself had started.

Check `ApplicationRef._runningTick` as well and return, the same way the
handler already bails out for a scheduled tick. The running tick needs no help
from the handler: its first pass in a zone app is already global, and if an
effect dirties a view mid-tick, `syncDirtyFlagsWithViews()` loops back for
another pass on its own. Rendering behaviour does not change, only the false
error goes away.

Added tests for both effect paths that fail without the fix.

Fixes angular#70984