Remove discrepancy in auto-ready behavior.

It's not clear why this variation in the auto-ready logic exists, and
the commit history doesn't seem to have any clues either. Perhaps the
actual readying up logic was incompatible with auto-ready at some point,
but at this point in time it doesn't seem like this is necessary at all,
and it appears to be causing a bug with the MobArenaStats extension.

By simply calling the player ready procedure regardless of the status of
the auto start timer, MobArena fires the arena player ready event that
MobArenaStats depends on for some of its pre-session bookkeeping. It
could be argued that MobArenaStats should be more robust, but we would
much rather fix the root problem than slack on the otherwise fairly
sound strictness of the MobArenaStats data model.

Fixes #746

src/main/java/com/garbagemule/MobArena/ArenaImpl.java

@@ -1310,11 +1310,7 @@ public class ArenaImpl implements Arena
 
     private void autoReady(Player p) {
         if (settings.getBoolean("auto-ready", false)) {
-            if (autoStartTimer.getRemaining() <= 0) {
-                playerReady(p);
-            } else {
-                readyPlayers.add(p);
-            }
+            playerReady(p);
         }
     }