Only consider chunks Loaded if at BORDER status

[aikar]

---

DOWNLOAD LINK: https://cdn.discordapp.com/attachments/748269415497465927/754945012080312370/loaded-chunks-r2.jar

While initial smoke test looks to be ok, this build presents a high risk of entity and tile entity lost if there is a bug that I did not see in my own testing.

It is super imperative that you have backups before testing this!

---

This greatly improves performance as it drastically reduces the amount
of Entities and Tile Entities that are "registered" into the world, as
purely "cached" chunks will no longer have their entities hanging out in the world.

Additionally this fixes our Entity Add To World and Entity Remove From World events

Those events have not been firing correctly since MC changed how chunks work here.

Now the server will only consider a chunk "loaded" if it's got a ticket putting
it at level 33 or lower, which matches the public Bukkit API.

---

Before this, there are a ton of chunks in memory in a 'cached' state, they aren't considered "loaded" in the api, they arent in any players view distance, are not force loaded.

When they are loaded and unloaded don't align with our expectation of "load/unload" events.

Leaving A LOT of extra entities in memory. meaning more entities to iterate for ticking (which will then be "skipped" because not in correct chunk") same with tile entities. also same issue applies for iterating chunks too, iterating far more than will end up being ticked resulting in a lot of checks to then skip it.

This change cuts it out so the iteration only operates on stuff in a loaded state now.

[aikar]

Updated test build with fix for the only reported crash so far. This specific detail wasnt the important part of testing, so took this one change out for now to keep build stable so we can test the important stuff

https://cdn.discordapp.com/attachments/748269415497465927/754945012080312370/loaded-chunks-r2.jar