Fix unhandledRejection handler: tighten pattern match, use nextTick for rethrow

- Use /request with tag.*timed out/ regex instead of .includes('timed out')
  to avoid suppressing unrelated timeout errors from other sources
- Use process.nextTick(() => { throw reason }) instead of bare throw inside
  the handler so non-lutron-leap rejections reliably crash the process
  (in Node.js 15+, throw inside unhandledRejection re-emits rather than exits)

Agent-Logs-Url: https://github.com/homebridge-plugins/homebridge-lutron/sessions/1d73447e-e125-477e-9d72-433b89c8167f

Co-authored-by: donavanbecker <9875439+donavanbecker@users.noreply.github.com>

Author: Copilot

src/Platform.HAP.ts

@@ -158,15 +158,17 @@ export class LutronCasetaLeap
           return
         }
         // lutron-leap LeapClient request timeout (an Error with a known message pattern)
-        if (reason instanceof Error && reason.message.includes('timed out')) {
+        if (reason instanceof Error && /request with tag.*timed out/.test(reason.message)) {
           this.log.debug('Suppressed lutron-leap request timeout (unhandled rejection):', reason.message)
           return
         }
-        // Unknown unhandled rejection — re-throw so Node.js handles it as fatal.
-        // This preserves the default crash behaviour for any rejection that is not
-        // a known lutron-leap artefact, preventing silent data loss.
+        // Unknown unhandled rejection — schedule a throw on the next tick so
+        // Node.js handles it as a fatal uncaught exception. Throwing directly
+        // inside the 'unhandledRejection' handler in Node.js 15+ causes a
+        // second unhandledRejection event rather than a process exit, so we
+        // use process.nextTick() to break out of the handler's call stack.
         this.log.warn('Unhandled promise rejection (not a known lutron-leap timeout):', reason)
-        throw reason
+        process.nextTick(() => { throw reason })
       })
     }