🐛 Handle null deadline in taskQueue requestIdleCallback

[thomas-lebeau]

Motivation

Some page-injected requestIdleCallback polyfills (e.g. setTimeout(cb, 0) in some WKWebViews) invoke the callback without an IdleDeadline argument. The current implementation assumes deadline is always defined and throws when accessing deadline.didTimeout, breaking the task queue.

Observed in SDK self-telemetry (US3, last 7d): ~89k TypeErrors across 6 customer orgs, 100% WebKit (iOS Mobile Safari, desktop Safari, Chrome Mobile iOS, and in-app WKWebViews), ~99.8% on SDK v6.32.0.

Sample stack trace:

TypeError: null is not an object (evaluating 'e.didTimeout')
  at e @ https://www.datadoghq-browser-agent.com/us3/v6/datadog-rum.js:1:73320
  at u @ https://www.datadoghq-browser-agent.com/us3/v6/datadog-rum.js:1:12650
  at <anonymous> @ https://www.datadoghq-browser-agent.com/us3/v6/datadog-rum.js:1:12602

Mapped to source: `taskQueue.ts` `run()` → `monitor.ts` `callMonitored` → `monitor.ts` wrapper.

Changes

• Accept `IdleDeadline | null` in the task queue `run` callback
• Treat a missing deadline the same as `didTimeout` (fall back to `MAX_EXECUTION_TIME_ON_TIMEOUT` budget)
• Add unit test covering the null-deadline case

Test instructions

• `yarn test:unit --spec packages/core/src/tools/taskQueue.spec.ts`
• Manually: override `window.requestIdleCallback` with `(cb) => setTimeout(cb, 0)` before SDK init and verify no runtime error.

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change.
• Added e2e/integration tests for this change.
• Updated documentation and/or relevant AGENTS.md file