Make the load balancer immediately aware of the number of playing players

[freyacodes]

This makes the load balancer more responsive to quick increases in player count, as it will not rely on outdated player data.

The current behavior leads to a sawtooth-esque patterns, like seen with this one node:

The original V1 client used this: https://github.com/freyacodes/Lavalink-Client/blob/master/src/main/java/lavalink/client/io/LavalinkLoadBalancer.java#L112

I have not tested this code yet.

[duncte123]

On first inspection this seems to do what you want it to do, will merge when you have the graphs of the test results.

Only concern I have is when a client gets connected to a node with other clients connected to it, this is not kept into account with this change

[freyacodes]

By testing I mean using it in a small environment to see if it is calculating penalties as expected. That graph has been taken from production, and it would be a while before this change lands there.

[duncte123]

By testing I mean using it in a small environment to see if it is calculating penalties as expected. That graph has been taken from production, and it would be a while before this change lands there.

That makes sense, if the test env gives the wanted results it's fine with me