feat(bridge): the faction table and an event's escort, ally and tether (runicnpc stage 5)

- npc.profiles answers with RunicNPC's faction table, and npc.profiles.set
  pushes one beside the profiles (RunicNpc_SetFactions), set first so the
  profiles are checked against it; a refused table comes back as
  factionsRefused and the old one is kept (D254);
- world.place with a profile takes escort (a Steam id; the player must be
  on, else escort-offline), ally ({kind: clan|player, id}) and tether (the
  run's own zone that holds the point, else no-zone), and gives each NPC
  its orders through RunicNpc_Escort, _Ally and _Tether. All or nothing:
  an order RunicNPC refuses removes every NPC the step placed (D269, D270,
  D272);
- the RunicNPC API the bridge needs is 4 (overlay.toml runicnpc_api = 4).

Compiled on the Oxide rig.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

overlay.toml

@@ -80,7 +80,7 @@ requires_plugins = ["Kits", "ZoneManager"]
 
 # ── The RunicNPC API the bridge needs ───────────────────────────────────────
 #
-# RunicNPC (docs/runicnpc/PLAN.md stage 4): the bridge's npc.* commands call
+# RunicNPC (docs/runicnpc/PLAN.md stages 4 and 5): the bridge's npc.* commands call
 # RunicNPC's API and need at least this version of it. It MUST equal
 # `RunicNpcApiNeeded` in RunicGateway.cs; `node scripts/checkPlugin.js` holds the
 # two equal. The release copies it into manifest.json, and the installer's
@@ -88,4 +88,4 @@ requires_plugins = ["Kits", "ZoneManager"]
 #
 # RunicNPC is optional to the bridge until its stage 9: without it every npc.*
 # command answers `runicnpc-missing`, and events place Rust's own scientists.
-runicnpc_api = 3
+runicnpc_api = 4