[1.16.5] Network set in TransmitterNetworkRegistry constantly growing

Issue description:

Basically, the title. private final Set<DynamicNetwork<?, ?, ?>> networks = new ObjectOpenHashSet<>(); On my public server this network collection grows larger over time, peaking at 50-100k objects. This eventually leads to TransmitterNetworkRegistry’s onTick method taking really long to complete. While investigating, I’ve found out that network is not always removed from this set even if all its transmitters were unloaded, so I believe it’s some sort of a leak. Is this behaviour intended/Is there some sort of a cleanup over time?

[KR33PYK1NG]

So, I was able to reproduce this issue locally and get to the bottom of it. Mekanism fully relies on onChunkUnloaded callback to clean up its networks. If the callback wasn’t executed in-time, the affected network will hang in memory until the server stops. Performant, on the other hand, does a deliciously cruel thing - it delays onChunkUnloaded execution if it’s considered laggy from Performant’s POV.

[pupnewfster]

I feel like odds are this is probably fixed by 10.3.2 due to our extra unload checks for when a chunk just becomes inaccessible but isn’t actually unloaded yet.