Remove non-zero BlockIterator block and Loading chunks earlier in player TP patches

Allowing only non-zero BlockIterators breaks an API contract explicitly allowing them
(*eyeroll*)

And loading chunks earlier in the TP patch did not resolve the original issue, and now
that it is resolved, shouldn't actually provide any tangible benefits

Spigot-API-Patches/Only-allow-non-zero-maxDistance-BlockIterators.patch

@@ -1,21 +0,0 @@
-From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
-From: Zach Brown <1254957+zachbr@users.noreply.github.com>
-Date: Tue, 12 Apr 2016 23:06:56 -0500
-Subject: [PATCH] Only allow non-zero maxDistance BlockIterators
-
-They can iterate infinitely causing the server to hang.
-Fix your plugins!
-
-diff --git a/src/main/java/org/bukkit/util/BlockIterator.java b/src/main/java/org/bukkit/util/BlockIterator.java
-index 0000000000000000000000000000000000000000..0000000000000000000000000000000000000000 100644
---- a/src/main/java/org/bukkit/util/BlockIterator.java
-+++ b/src/main/java/org/bukkit/util/BlockIterator.java
-@@ -0,0 +0,0 @@ public class BlockIterator implements Iterator<Block> {
-      *
-      */
-     public BlockIterator(World world, Vector start, Vector direction, double yOffset, int maxDistance) {
-+        com.google.common.base.Preconditions.checkArgument(maxDistance != 0, "maxDistance cannot be 0!"); // Paper - Only allow non-zero maxDistance
-         this.world = world;
-         this.maxDistance = maxDistance;
- 
---