Predict dumping (#32394)

* Predict dumping

- This got soaped really fucking hard.
- Dumping is predicted, this required disposals to be predicte.d
- Disposals required mailing (because it's tightly coupled), and a smidge of other content systems.
- I also had to fix a compnetworkgenerator issue at the same time so it wouldn't mispredict.

* Fix a bunch of stuff

* nasty merge

* Some reviews

* Some more reviews while I stash

* Fix merge

* Fix merge

* Half of review

* Review

* re(h)f

* lizards

* feexes

* feex

Content.Client/Power/EntitySystems/PowerReceiverSystem.cs

@@ -3,6 +3,7 @@ using Content.Client.Power.Components;
 using Content.Shared.Power.Components;
 using Content.Shared.Power.EntitySystems;
 using Content.Shared.Examine;
+using Content.Shared.Power;
 using Robust.Shared.GameStates;
 
 namespace Content.Client.Power.EntitySystems;
@@ -26,9 +27,20 @@ public sealed class PowerReceiverSystem : SharedPowerReceiverSystem
         if (args.Current is not ApcPowerReceiverComponentState state)
             return;
 
+        var powerChanged = component.Powered != state.Powered;
         component.Powered = state.Powered;
         component.NeedsPower = state.NeedsPower;
         component.PowerDisabled = state.PowerDisabled;
+        // SO client systems can handle it. The main reason for this is we can't guarantee compstate ordering.
+
+        if (powerChanged)
+            RaisePower((uid, component));
+    }
+
+    protected override void RaisePower(Entity<SharedApcPowerReceiverComponent> entity)
+    {
+        var ev = new PowerChangedEvent(entity.Comp.Powered, 0f);
+        RaiseLocalEvent(entity.Owner, ref ev);
     }
 
     public override bool ResolveApc(EntityUid entity, [NotNullWhen(true)] ref SharedApcPowerReceiverComponent? component)