Expand the end-to-end suite from 7 tests to 39

[milanmalhotra]

Closes #76

Takes the end-to-end suite from 7 tests to 39, running in about twenty seconds.
The new cases cover what MockBukkit cannot reach rather than restating the 389
unit tests: real Brigadier permission gating, the teleport countdown and its
cancel, inventory clicks from a real client, two players at once, and the nether
and the end.

It found a bug

The GUI rename prompt crashes on Paper 1.21.11. AnvilGUI's static initializer
looks up net.minecraft.world.entity.player.EntityHuman, the Spigot mapped
name, and Paper serves Mojang mappings, so clicking Rename throws
NoClassDefFoundError and the prompt never opens. Filed as #77 with the stack
trace.

The spec that found it is written and works right up to the crash. It is held
out of this pull request so the suite stays green, and goes in with the fix.

The fixture change

The harness disabled the teleport delay, cancel-on-move, safety and the
max-homes cap so an assertion could never race a timer, which left all four
untested. They are on now, and no existing test needed changing, because a
holder of sh2.bypass-teleport-delay takes a delay of 0 and a holder of
sh2.bypass-max-homes skips the cap, both under sh2.admin.

Granting sh2.player to everyone rather than to ops gives the specs two tiers:
a bot that calls makeOp() keeps the instant, uncapped path, and one that does
not exercises the real behavior. sh2.move-home is pinned to op so a spec can
prove PermissionOverrides detaches a node from its bundle.

Coverage

Spec	Tests
permissions.spec.ts	5
teleport.spec.ts	5
gui.spec.ts	5
admin.spec.ts	5
blacklist.spec.ts	4
worlds.spec.ts	4
maxhomes.spec.ts	3
items.spec.ts	2

Two helpers: dimensions.ts clears and floors a pocket before teleporting,
since the generator decides what is at any spot in the nether and
teleportSafety refuses a home inside blocks. menus.ts opens a home's
management menu, which needs a raw mineflayer right click because the locator
API clicks with the left button only.

Left out

Pagination. Forty-six sequential /create-home calls risk Paper's chat spam
kick, and HomesGuiPaginationTest already covers it in process.

The homes spec's permission test is gone. Its premise was that a non-op holds
nothing, which the fixture change makes untrue; permissions.spec.ts covers
that ground against an admin command instead.

Noticed while working, not addressed here

TeleportAttemptsDao compares the stored location to the current one with exact
double equality, so any position change at all cancels a pending teleport. An
idle bot sending position packets was enough, which is why specs that stand
still through the countdown set bot.physicsEnabled = false. On a live server
that means standing on a boat or a piston would cancel a teleport.

PlayerMoveWhileTeleporting never sets canTeleport; it only logs. The cancel
actually happens in the DAO on each countdown tick, so the listener is querying
SQLite on every move event while doing nothing functional. That may make #46
larger than it reads.

Testing

mvn -B clean package -DskipTests
./gradlew plugwrightTest

39 passed, 0 failed, 18.5s.