useNitroQuery: add accept() predicate; migrate two mod-tools chatlog views

Many composer/parser pairs on the Nitro wire are correlation-key based:
the request carries a key (roomId, issueId, etc.) and the response shows
up on the globally-shared event bus, where other components may be
listening for the same parser type with a different key. The previous
useNitroQuery resolved on the FIRST matching parser event regardless of
key — useless for that pattern, which is why two obvious migration
targets (ModToolsChatlogView, CfhChatlogView) were skipped earlier.

Adapter change
- New optional `accept?: (event) => boolean` on NitroQueryConfig.
- In awaitNitroResponse, events for which accept returns false are
  IGNORED rather than resolving the promise. The listener stays
  registered, the timeout still applies. This lets callers do:
    accept: e => e.getParser()?.data.roomId === roomId

Migrations
- src/components/mod-tools/views/room/ModToolsChatlogView.tsx
  - Was: useState<ChatRecordData>(null) + useMessageEvent with
    `if (parser.data.roomId !== roomId) return; setRoomChatlog(...)` +
    a mount-only useEffect dispatching the composer.
  - Now: a single useNitroQuery call keyed on roomId; accept filters
    by roomId; the query is enabled only when roomId is set.
    The composer is no longer re-dispatched on remount within
    staleTime; switching to a different room still triggers a fresh
    fetch because the queryKey changes.
- src/components/mod-tools/views/tickets/CfhChatlogView.tsx
  - Same pattern, keyed on issueId.

Both migrations drop ~15 lines per file (no more local state + manual
listener + manual send) while gaining cache/dedup/loading/error
handling from TanStack Query.

Verification
- yarn eslint on the four files: 1 pre-existing error (the
  IMessageEvent "redundant union" false positive in createNitroQuery
  that we already documented — local sandbox doesn't have the
  renderer SDK installed, so its types resolve as `any`).
- yarn test: 49/49 passing.
- yarn tsc on the four files: clean.

src/components/mod-tools/views/room/ModToolsChatlogView.tsx

@@ -1,8 +1,7 @@
 import { ChatRecordData, GetRoomChatlogMessageComposer, RoomChatlogEvent } from '@nitrots/nitro-renderer';
-import { FC, useEffect, useState } from 'react';
-import { SendMessageComposer } from '../../../../api';
+import { FC } from 'react';
+import { useNitroQuery } from '../../../../api/nitro-query';
 import { DraggableWindowPosition, NitroCardContentView, NitroCardHeaderView, NitroCardView } from '../../../../common';
-import { useMessageEvent } from '../../../../hooks';
 import { ChatlogView } from '../chatlog/ChatlogView';
 
 interface ModToolsChatlogViewProps
@@ -14,22 +13,16 @@ interface ModToolsChatlogViewProps
 export const ModToolsChatlogView: FC<ModToolsChatlogViewProps> = props =>
 {
     const { roomId = null, onCloseClick = null } = props;
-    const [ roomChatlog, setRoomChatlog ] = useState<ChatRecordData>(null);
 
-    useMessageEvent<RoomChatlogEvent>(RoomChatlogEvent, event =>
-    {
-        const parser = event.getParser();
-
-        if(!parser || parser.data.roomId !== roomId) return;
-
-        setRoomChatlog(parser.data);
+    const { data: roomChatlog } = useNitroQuery<RoomChatlogEvent, ChatRecordData>({
+        key: [ 'nitro', 'mod-tools', 'room-chatlog', roomId ],
+        request: () => new GetRoomChatlogMessageComposer(roomId),
+        parser: RoomChatlogEvent,
+        accept: e => e.getParser()?.data.roomId === roomId,
+        select: e => e.getParser().data,
+        enabled: roomId !== null
     });
 
-    useEffect(() =>
-    {
-        SendMessageComposer(new GetRoomChatlogMessageComposer(roomId));
-    }, [ roomId ]);
-
     if(!roomChatlog) return null;
 
     return (