ServerKickEvent discrepencies

Waterfall improved the ServerKickEvent to cover more cases, (#39), this is great because it lets plugins capture certain situations easier than vs bungee, however;

Specifically, the LOST_CONNECTION cause is generic and fired should the client disconnect from the client, leading to a specific edge case which plugins do not expect: The client has disconnected from the server

I guess this opens a question of what is the best way to go for this:

1. Move lost connection to its own event, this could technically also be configured to support the older way of ServerKickEvent capturing this

2. Does a LOST_CONNECTION cause really fall under a server kick event? (Too generic vs server kick which imples that the player was actually kicked, not that we just closed the connection) (Or, would this fall into 1, maybe without backwards compat)

Start by reviewing ServerKickEvent, the LOST_CONNECTION cause, and the Waterfall improvement referenced as #39. Compare the two proposed approaches, including backward compatibility, and clarify which client-disconnect behavior should be represented. Done means the event semantics and compatibility decision are settled and reflected in the project.