Stream deferred visual nodes in camera-distance order (nearest first)

The progressive load previously streamed the deferred visual nodes (3d model
instances + terrain shapes/lines) in file order, so distant scenery could load
before the player's surroundings. This builds them nearest-camera first instead.

The visual pass now runs in two steps. Enumeration replays the twin and captures
each visual node verbatim (its resolved tokens as text -- numbers round-trip
losslessly through cParser) together with the transform/group context it was read
under and, for models, its transformed world position. Once the replay is
exhausted the records are sorted by squared distance to the camera (terrain shapes
first so the ground appears before the props on it), then built a budgeted slice
per frame through the normal node path with the captured transform and group
restored -- so placement, grouping and the per-cell instance buckets come out
identical to an in-order load.

Two supporting fixes make out-of-order/late insertion correct:
- a cell/section whose geometry was already baked (the renderer finalised it
  before a deferred node arrived) now appends the new shape/lines straight into
  its live geometry bank instead of merging into vertex-freed geometry, which
  would silently drop it; create_geometry() remembers the bank for every cell.
- events that bind to visual model instances (lights/animation/texture/visible)
  are deferred from InitEvents() to a new InitInstanceEvents() run after the
  visual nodes are built, so their target models exist when they initialise.

Verified on td.scn: playable ~2s, 540 deferred nodes enumerated and built
nearest-first ~0.5s later, no duplicate instances.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

world/Event.cpp

@@ -2493,6 +2493,21 @@ void
 event_manager::InitEvents() {
     //łączenie eventów z pozostałymi obiektami
     for( auto *event : m_events ) {
+        // events binding to model instances are deferred: with progressive loading their
+        // target models stream in after this (infrastructure) pass, so binding them now
+        // would fail. InitInstanceEvents() initialises them once the visuals are in place.
+        if( true == event->binds_to_instances() ) { continue; }
+        event->init();
+        if( event->m_delay < 0 ) { AddToQuery( event, nullptr ); }
+    }
+}
+
+// initializes the events deferred by InitEvents() (those binding to model instances),
+// after the (progressively loaded) visual nodes have been built so the models exist.
+void
+event_manager::InitInstanceEvents() {
+    for( auto *event : m_events ) {
+        if( false == event->binds_to_instances() ) { continue; }
         event->init();
         if( event->m_delay < 0 ) { AddToQuery( event, nullptr ); }
     }