feat(communication): housekeeping find-user-by-id composer

OutgoingHeader.HOUSEKEEPING_FIND_USER_BY_ID = 9101 with a one-int
payload. The response side reuses HousekeepingUserDetailEvent (no new
parser) — find-by-id and find-by-name converge on the same shape
because the server has nothing different to say about a user found
via numeric id vs. via username lookup.

vitest 138/138, `yarn compile:fast` clean.

packages/communication/src/messages/outgoing/OutgoingHeader.ts

@@ -525,4 +525,5 @@ export class OutgoingHeader
 
     // Housekeeping (in-client admin panel) — IDs 9100..9199 reserved
     public static HOUSEKEEPING_FIND_USER_BY_NAME = 9100;
+    public static HOUSEKEEPING_FIND_USER_BY_ID = 9101;
 }

packages/communication/src/messages/outgoing/housekeeping/HousekeepingFindUserByIdComposer.ts

@@ -0,0 +1,21 @@
+import { IMessageComposer } from '@nitrots/api';
+
+export class HousekeepingFindUserByIdComposer implements IMessageComposer<ConstructorParameters<typeof HousekeepingFindUserByIdComposer>>
+{
+    private _data: ConstructorParameters<typeof HousekeepingFindUserByIdComposer>;
+
+    constructor(userId: number)
+    {
+        this._data = [userId];
+    }
+
+    public getMessageArray()
+    {
+        return this._data;
+    }
+
+    public dispose(): void
+    {
+        return;
+    }
+}

packages/communication/src/messages/outgoing/housekeeping/index.ts

@@ -1 +1,2 @@
+export * from './HousekeepingFindUserByIdComposer';
 export * from './HousekeepingFindUserByNameComposer';