Use Location for integration canLeash checks and enforce claim checks for fence leashing

[SrBedrock]

Refactor integration permission checks to use Location instead of LivingEntity. Changed Integration.canLeash(Location, Player) and updated IntegrationManager, all integration implementations (WorldGuard, GriefDefender, GriefPrevention, Lands, Residence, Towny) and callers to pass a Location (e.g. entity.getLocation() or target.getLocation()). Also updated Tether event registration to supply integrationManager to PlayerInteractListener and made various cosmetic adjustments (added final modifiers and small local refactors). No functional behavior changes intended—this decouples integrations from entity objects and centralizes location-based permission checks.

Inject IntegrationManager and perform a canLeash(location, player) check before calling handleFenceLeashing so mobs can't be leashed in protected/claimed areas. Also add a null check for clickedBlock, import Location/Player types, and update the constructor and method params to accept/use the IntegrationManager and final modifiers. Added imports for leash-related exceptions (prepared for future error handling).

Update GriefPreventionIntegration to lazy-initialize its DataStore via a new getDataStore() method and replace direct dataStore accesses to avoid null issues. Clean up IntegrationManager imports to explicitly reference toggleable integration classes and remove unused imports.

[SrBedrock]

@NaspoDev there is a critical bug where players can steal mobs trapped in fences inside protected areas.

[NaspoDev]

Hi @SrBedrock, thanks for the PR.

The core of your changes are good, but I'd like to request some changes to your PR before I test and potentially merge it.

1. Your comment changes to Integration.canLeash() denote that this can only be used for mobs, when it is in fact also used for players, hence the use of LivingEntity before. Please change the wording to "target" instead of "mob".
2. The IntegrationManager.canLeash() check for fence leashing should happen in LeashMobService.handleFenceLeashing(), like all the other related checks. Not in PlayerInteractListener.
3. Undo your changes of using explicit imports instead of broad imports. Everywhere that broad imports are used is for a good reason. For example, IntegrationManager will always need all integrations.
4. Your excessive use of final makes things harder to read and is just not really necessary. It especially makes it harder to review this PR, so please undo all excessive uses of the final keyword.

[NaspoDev]

@NaspoDev there is a critical bug where players can steal mobs trapped in fences inside protected areas.

When you say "trapped in fences" do you mean the fence leashing feature? If so, I'm assuming it's this PR that also addresses that with the claim checks?

If it's something else, please open a separate issue for it (or make another PR if you like).

[SrBedrock]

@NaspoDev there is a critical bug where players can steal mobs trapped in fences inside protected areas.

When you say "trapped in fences" do you mean the fence leashing feature? If so, I'm assuming it's this PR that also addresses that with the claim checks?

If it's something else, please open a separate issue for it (or make another PR if you like).

Yes, this PR adress the issue.

[NaspoDev]

Okay, well let me know if you're planning on making those changes I requested. Otherwise I'll just go ahead and fix it myself. Thanks!