BACKPORT: ServerTickScheduler

[johnmoney]

Instead of: everything running an update() things like AI does not need 30 Hz . Combat resolution does not need render-rate precision. Expensive systems are capped by design. Budget-aware degradation with Long-term stability in mind.

[johnmoney]

@Riryan when you get a chance, can you checkout this branch?

I am pretty sure all the changes are made from the zip in the old NB forum. Build does not have monster pursue with default MonsterActivityComponent, not seeing wander either.

[Riryan]

I've made some improvements to the core parts, would still need to check the hooks though

[Riryan]

Core improvements:

• monotonic server clock with raw and clamped delta

• validated scheduler/channel configuration

• deterministic channel/system ordering

• per-channel and per-system metrics snapshots

• diagnostics report builder
  With [SerializeField] private bool logDiagnostics;
  you get a runtime text dump of scheduler health

• failure isolation across Prepare/Execute/Commit

• explicit Shutdown/Clear/Unregister lifecycle

• load-shedding extension hook via ILoadSheddingTickSystem

• safe delayed-task handles with generation validation

• delayed-task callback/time budgets

• deterministic delayed-task ordering for identical ExecuteAt times

• GameplayTimers channel separated from LowFreq

• optional reflection registration for project-specific systems
  TryRegisterByTypeName(scheduler, "MultiplayerARPG.Server.Runtime.MonsterActivityCombatSystem", "Combat", 20, 0);
  This means
  scheduler = the scheduler instance to register into
  "MultiplayerARPG.Server.Runtime.MonsterActivityCombatSystem" = full type name to search for
  "Combat" = scheduler channel name
  20 = priority
  0 = order inside that channel
  Notes:

• Use scheduler.CaptureSnapshot() or scheduler.BuildDiagnosticsReport() for runtime health reporting.