Version 2.0 will drop support for Spigot and BungeeCord / Waterfall -- Must use Paper or Velocity

[A248]

The title tells you what you need to do.

For LibertyBans 2.0, we are planning to drop support for plain Spigot, BungeeCord, and Waterfall.

1. If you're using Spigot, you will have to switch to Paper.
2. If you're using BungeeCord or Waterfall, switch to Velocity.

[A248]

Benefits

1. Fewer platforms to support and debug; less conditional code
2. Expose Components in the Java API
3. BungeeCord and Waterfall are fundamentally broken when plugin listeners and commands are concurrently re-registered at runtime (affects /libertybans restart)
4. Can rely on Slf4j everywhere, without logging abstraction

These are small wins. There is a bigger motivation for this issue, I think, which I forgot to write down.