fix: bootstrap NG0210 when the runtime exposes a global PerformanceObserver - #178

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. (No issue filed — found while updating an app to @nativescript/ios 9.1.0-alpha.20.)
• You have signed the CLA.
• All existing tests are passing. (The device suite was not run locally; CI runs it on both platforms.)
• Tests for the changes are included.

What is the current behavior?

Every debug boot fails on runtimes that ship a Web Performance API (e.g. @nativescript/ios 9.1.0-alpha.20, which does g.PerformanceObserver = PerformanceObserver):

NG0210: The document object is not available in this context.
Make sure the DOCUMENT injection token is provided.
    at getDocument (deps-bundle.mjs)
    at _ImagePerformanceWarning.start (deps-bundle.mjs)

Angular starts ImagePerformanceWarning at the end of internalCreateApplication whenever ngDevMode is on, and the service only bails out early in three cases:

start() {
  if (ngServerMode || typeof PerformanceObserver === 'undefined' || (bothWarningsDisabled)) return;
  this.observer = this.initPerformanceObserver();
  const doc = getDocument();   // NG0210

The missing PerformanceObserver global is what used to keep this off our path. Once the runtime defines it, the service falls through to getDocument() — which reads a module-scoped variable set by Angular's internal setDocument(), not the DOCUMENT DI token we provide via NativeScriptDocument — and throws.

What is the new behavior?

NATIVESCRIPT_MODULE_PROVIDERS now defaults IMAGE_CONFIG to disabling both image warnings, which restores the early return. That array feeds both NativeScriptModule and createProvidersConfig, so the NgModule and standalone bootstrap paths are both covered.

Both flags are required — Angular ANDs them. The provider has to live in the app/environment injector rather than COMMON_PROVIDERS, because IMAGE_CONFIG is declared providedIn: 'root' and the root environment injector self-satisfies it from the token's own factory instead of delegating to the platform injector.

The warnings scan the DOM for oversized and lazily-loaded <img> elements, so they can never produce a meaningful result under NativeScript. Apps that want them back can still provide their own IMAGE_CONFIG — app providers are applied after the NativeScript ones.

Verified against Angular 21.2.x and 22.0.x: the guard is identical in both, and IMAGE_CONFIG is public API on @angular/common in both.