Account Socket.IO messaging-many skipped corpus

Bun compatibility slice

Account for js/third_party/socket.io/socket.io-messaging-many.test.ts at exhaustive corpus position 4053.

Bun currently disables the entire 20-case suite with describe.skip because the upstream cases hang. Home should:

• resolve its Socket.IO support import correctly;
• preserve Bun's suite-level skip rather than changing upstream intent;
• report the skipped describe block as an explicit suite-level todo, with no unsupported or allowed-empty classification;
• add the fixture to the permanent third-party matrix so any upstream reactivation becomes observable.

Tracked from #66.

Implemented and pushed in 181e30937.

Home now resolves the extensionless Socket.IO support import, preserves Bun's intentional suite-level describe.skip, and permanently asserts the resulting one explicit suite todo instead of classifying the file as unsupported or allowed-empty.

Verification:

• focused position 4053: 1 file, 0 failed, 1 todo, 0 unsupported/allowed-empty;
• Socket.IO positions 4050–4053: 4 files, 13 passed, 5 explicit todos, 0 failed/unsupported/allowed-empty;
• permanent gRPC error-stack, SQL adapter-contract, third-party corpus, and 35-case diagnostic suites all pass.