Fix lazymc never recognizing the Forge server as ready

Missing forge = true under [server] meant lazymc couldn't parse the
Forge status response (extra embedded mod-list payload vanilla
doesn't have), so it never detected the backend as online and always
showed the "still starting" kick screen. Also documents the inherent
~25-30s client-timeout race on the very first cold-boot connection.

server/setup-server.sh

@@ -83,6 +83,7 @@ cat > "$BASE_DIR/lazymc.toml" <<EOF
 [server]
 directory = "$SERVER_DIR"
 command = "bash run.sh nogui"
+forge = true
 address = "127.0.0.1:${MC_INTERNAL_PORT}"
 freeze_process = false
 wake_whitelist = false