Motivation for the change, related issues

The tab coordinator was causing an infinite loop of broadcast messages, where checkForExistingTabs was being called repeatedly. This resulted in continuous ping messages being sent between BroadcastChannel instances, even within a single tab.

The issue had two contributing factors:

1. Multiple BroadcastChannel instances (one in tab-coordinator.ts, another in useTabTracking hook) could trigger each other
2. An unstable useCallback dependency in useTabTracking caused the effect to re-run on every render

Implementation details

tab-coordinator.ts:

• Added mutex lock (isCheckingTabs) to prevent concurrent calls to checkForExistingTabs
• Added rate limiting (lastCheckTime + 1 second minimum interval) to prevent rapid successive calls
• Reset these guards in destroyTabCoordinator for proper cleanup

use-tab-tracking.ts:

• Fixed unstable useCallback dependency by storing options.onWorkerLost in a ref
• Changed checkWorkerLost callback to have empty dependencies [] instead of [options]

Testing Instructions (or ideally a Blueprint)

1. Open Personal WordPress Playground
2. Open browser DevTools console
3. Paste this to monitor broadcast messages:

const originalPostMessage = BroadcastChannel.prototype.postMessage;
BroadcastChannel.prototype.postMessage = function(message) {
  console.log('%c📤 SEND', 'color: #4CAF50; font-weight: bold', this.name, message);
  return originalPostMessage.call(this, message);
};

4. Verify that ping messages are NOT being sent continuously (should only see initial pings on load, then silence)
5. Open a second tab with the same site - verify tabs detect each other properly

cc @fellyph since you also observed this!