Better handle not failing over on a read timeout

The existing Velocity logic was pretty optimistic, hoping the player connection would stay alive long enough to accept a connection to another server. Now, if we notice a read timeout on the server end, we'll treat the disconnect as "unsafe" and disconnect the player immediately.

I've added a configuration option to solve the issue in the way BungeeCord does it. This could cause issues with servers that extensively modify the server pipeline and could degrade the user experience, though. Let's try this more conservative and see if it helps,

api/src/main/java/com/velocitypowered/api/event/player/KickedFromServerEvent.java

@@ -209,7 +209,7 @@ public final class KickedFromServerEvent implements
       return LegacyText3ComponentSerializer.get().serialize(message);
     }
 
-    public net.kyori.adventure.text.Component getMessageComponent() {
+    public net.kyori.adventure.text.@Nullable Component getMessageComponent() {
       return message;
     }