fix InitialHandler exception handling behaivour

[Outfluencer]

checking if its possible to send a kick message and sending it to the client is useless here as it would call the delayed close method that would send the packet 250ms delayed but the handlerboss would close it immediately. Also no need to call the channelwrapper close method here because the handler boss will close as i said and we only need to mark closed

[Outfluencer]

@md-5

[Janmm14]

I think we should make it so it still sends disconnect packet.

[Outfluencer]

but it would never do, we need to wait the 250ms to send a kick message otherwise it would be buggy and i think waiting when encountering an exception is not very good.
also i saw that the channelInactive method of the HandlerBoss also markes the channel as closed so we could remove the full method without a difference just less code executed

Edit: my bad, sending it directly with unsafe.sendPacket works in this case, so i will add it and send it without delay, the handler boss will directly close it after we send the kick packet, cause the handler boss will close it instantly anyway waiting 250ms would make no sense at all

[Outfluencer]

@md-5
the handler boss will close the connection
https://github.com/SpigotMC/BungeeCord/blob/8a88ce464e0b107b15523109afd7810096e635ca/proxy/src/main/java/net/md_5/bungee/netty/HandlerBoss.java#L210C13-L210C25

after the close, the channelInactive is called, and the channelwrapper is marked as closed.
https://github.com/SpigotMC/BungeeCord/blob/8a88ce464e0b107b15523109afd7810096e635ca/proxy/src/main/java/net/md_5/bungee/netty/HandlerBoss.java#L61C21-L61C31

so closing the channel with the disconnect methode is unnecessary.
it delays the packet sending by 250 ms but the channel is already closed and marked as closed
The kick packet will never be sent to the client.

this pr removes the disconnect method calls and tries to send the kick packet instantly so the client has a chance to see the kick message