fix(js): reject unknown createEvent interfaces

[xrip]

Summary

• throw NotSupportedError for unknown Document.createEvent interface names instead of returning a generic Event
• make Event, Events, HTMLEvents, and SVGEvents explicit aliases
• map the already-exposed HashChangeEvent and MessageEvent constructors
• keep existing type-aware event extensions and case-insensitive matching

The DOM createEvent algorithm requires an unknown name, or a listed interface that is not exposed on the current global, to throw NotSupportedError.

Fixes #610

Verification

• the new unknown-name regression fails on unchanged origin/main
• focused createEvent tests: 5/5 passed
• render obscura-js: 367/367 passed
• no-render obscura-js: 281/281 passed
• full render workspace: 1397/1398 passed, 4 skipped
  • only max_connections_refuses_then_recovers failed; it also fails on the unchanged Windows baseline and is tracked by Windows connection refusal resets before the 503 response is read #604 with a fix in fix(cdp): deliver connection refusal response #605
• release CLI builds passed for render, render,stealth, no default features, and no default features plus stealth
• direct CLI probe confirmed a real NotSupportedError DOMException, all four aliases, and the HashChangeEvent and MessageEvent classes
• obstacle course: 33/33 with benchmark PR fix(obstacle-course): reobserve intersection sentinel obscura-benchmark#3 and the fixture normalization recorded there