Initialize engine-side TriSurf allocators (#108)

[themuffinator]

What changed

• Initialize the engine/tool copy of the render-geometry TriSurf allocators after renderer data setup and before startup scripts can invoke a tool command, then release it during common shutdown.
• Make the TriSurf lifecycle idempotent so static-renderer builds safely share the renderer-initialized copy while module builds retain independent renderer and tool copies.
• Keep static-renderer allocation hooks and counters paired by preventing engine/tool initialization before the renderer installs its hooks.
• Add a focused lifecycle/order/source-partition contract and register it in local, commit, and push validation.
• Add the user-facing release-completion entry.

Root cause

The v0.10 crash dump was symbolized against the exact shipped engine PDB. dmap game/airdefense1.map crashed in idDynamicBlockAlloc<idDrawVert>::AllocInternal() while deriving a light polytope. After renderers became runtime modules, openq4_render_geo is linked once into the client and independently into each renderer. Renderer startup initialized only the renderer module's file-static allocator copy; built-in dmap used the client copy, which remained uninitialized.

Validation

• Full Windows rebuild after the lifecycle-order hardening: 1145/1145 targets; client, dedicated server, SP/MP GameLibs, OpenGL renderer, and Vulkan renderer linked
• python tools/tests/dmap_render_geometry_lifecycle.py
• python tools/tests/renderer_vulkan_md5r_compatibility.py
• documentation, charset, validation-hardening, Python compile, and diff checks
• Fresh windowed/no-input stock-assets runtime after the final change: dmap -noCM -noAAS game/airdefense1 completed in 3 seconds, reported the stock map leak normally, and shut down cleanly without an allocator or lifecycle error
• No fullscreen launch, input injection, or OS capture was used

Fixes #108

[themuffinator]

Final hosted validation for 9f6cce0: 21 checks passed, 4 failed, 0 pending. Commit Validation and ARM64 Cross Build passed completely, including Windows/Linux builds, ASan/UBSan, all four macOS thin builds, and both universal2 assembly/package/dedicated-smoke jobs. The four red macOS Push Verification jobs exactly reproduce main baseline renderer-default-safety diagnostics and contain no TriSurf allocator or lifecycle failure.