Log more information when a safe starting location can't be found

The current implementation of LocationUtils#findRandomSafeLocation "gives up" after 20 tries: https://gitlab.com/uhccore/uhccore/-/blob/a5d2993bcc5e5dd96a7e290cc132379e86fd4360/src/main/java/com/gmail/val59000mc/utils/LocationUtils.java#L43

If this happens, players will be spawned at a random location, at y=250, and fall down. There have been reports on the Discord server of players being spawned high up in the air, which would suggest that this can actually happen. Obviously, it can, but presumably the previous author decided that it was highly unlikely to happen unless something went wrong.

At the very least, we should log some more information to the server console when this happens, such as the fact that it happened at all, and a list of locations that were tried (but not considered safe). It would also be useful to log the world seed and Minecraft version, and whether or not replace-ocean-biomes is enabled, so we can easily reproduce the issue when debugging.

We could also introduce a config option to allow server owners to tweak the number of tries given to findRandomSafeLocation. But normally I would think that 20 tries is good enough. If there's a bug or a problem causing the algorithm to fail in finding a safe location in 20 tries, it would be better for us to find it, rather than ignoring the problem and allowing more and more tries.

Edited by Odin Dahlström