TNT placed outside of a claim will still break blocks inside of a claim

[Draylar]

My latest commit offers 2 checks to prevent TNT griefing:

• TntEntityMixin, which straight out stops TNT explosions if their origin is within a claim you don't have permissions in.
• ExplosionMixin, which checks each position inside an explosion if it goes off to ensure none go over into another claim you don't have permissions in.

This works, but there's a bit of desync on the client. This is because ExplosionS2CPacket doesn't send information about the "causing entity", which means the client thinks there was no cause (= good to go, break the blocks!). This should only occur in very rare cases, but I'd still like to patch it before marking this issue as closed.

ExplosionMixin is also currently basically a soft override; ideally, it would be switched to a single inject in the future.

[dandin87]

AoF 3 2.6.10 Redstone activated TNT dropped from above will destroy blocks in the claim. It also appears that TNT ignited next to the claim will also break blocks inside the claim. Also, Diggus maximus vein mine apparently bypasses claims, which I thought was fixed at some point but is somehow not anymore. Note that we do have Delta Logger and I will try and test without it to see if its interfering.