Fixed Ender Dragon using wrong tracking range

[roro1506HD]

This commit (Initial update to EAR patch) has changed how monsters are detected (then org.spigotmc.ActivationRange, now io.papermc.paper.entity.activation.ActivationRange):

-        } else if (entity instanceof Monster || entity instanceof Slime) {
+        } else if (entity instanceof Enemy) { // Paper - correct monster check

Tracking range (org.spigotmc.TrackingRange) is also affected by this change since it has the following code under the MISC activation type:

            if (entity instanceof net.minecraft.world.entity.boss.enderdragon.EnderDragon) {
                // Exempt ender dragon
                return ((ServerLevel) entity.level()).getChunkSource().chunkMap.serverViewDistance;
            }

Now, it turns out the net.minecraft.world.entity.boss.enderdragon.EnderDragon class implements Enemy which makes it use the MONSTER activation range and not the server view distance.

This PR moves the Ender Dragon check above the activation type check so that it returns the right tracking range, but still making the Ender Dragon activation range the same as monsters.

[roro1506HD]

Seems not to be working as expected, doing some more tests