refactor: replace reflection with direct Folia API calls

[roomote-v0]

Replaces all reflection-based Folia scheduler calls with direct API calls, as requested.

Changes

• pom.xml: Added PaperMC repository and dev.folia:folia-api as a provided dependency so Folia types are available at compile time
• SchedulerAdapter.java: Rewrote to use direct Folia API calls instead of reflection. Folia-specific code is isolated in a static inner class (FoliaScheduling) so the JVM only loads Folia types when actually running on a Folia server. On Paper/Spigot servers, those classes are never touched.

How it works

Java lazily loads classes -- the FoliaScheduling inner class (which references ScheduledTask, getGlobalRegionScheduler(), etc.) is only loaded by the JVM when one of its static methods is called. Since those methods are only called when IS_FOLIA is true, Paper/Spigot servers never trigger class loading of Folia types.

What was removed

• All java.lang.reflect.Method fields and invocations
• All Class.forName() lookups
• The initializeFoliaReflection() method
• The reflection-based FoliaTaskWrapper (replaced with a typed version)

The public API (runTimer, runLater, runAsync, runForEntity, TaskWrapper) is unchanged, so no caller modifications are needed.

---

View task on Roo Code Cloud

[roomote-v0]

Rooviewer   See task

The latest commit (47d512e) restores SchedulerAdapter.java, fixing the compilation issue. Two issues from previous reviews remain open.

• SchedulerAdapter.java was deleted but is still referenced by AutoSaveScheduler, ConfirmScheduler, and SqlStorageImpl -- project will not compile
• Folia detection uses AsyncScheduler which also exists on Paper 1.20+ -- should check for a Folia-only class like RegionizedServer instead
• ConfirmScheduler passes a null retired callback to the entity scheduler, so player disconnects before timeout leak entries in the confirmingPlayers map

Previous reviews

• 825ac0d: Review #1
• 83f8911: Review #2

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote-v0]

AsyncScheduler exists on Paper 1.20+ (Paper adopted the Folia scheduler APIs for forward compatibility), so IS_FOLIA will be true on modern Paper servers as well. This causes the plugin to take the Folia scheduling path on Paper, which happens to work today but is fragile since it depends on Paper's compatibility layer rather than the native Bukkit scheduler. The standard way to detect Folia specifically is to check for a Folia-only class like io.papermc.paper.threadedregions.RegionizedServer.

Suggested change

	Class.forName("io.papermc.paper.threadedregions.scheduler.AsyncScheduler");
	Class.forName("io.papermc.paper.threadedregions.RegionizedServer");

_{Fix it with Roo Code or mention @roomote and request a fix.}

[roomote-v0]

On Folia, entity.getScheduler().runDelayed() is called with a null retired callback (the third argument inside FoliaScheduling.runForEntity). If the player disconnects before the timeout fires, the task is silently discarded and confirmationsManager.removeConfirmingPlayer(player) never runs. Since there is no PlayerQuitEvent handler that cleans up confirming players either, the entry leaks in the confirmingPlayers map for the lifetime of the server. The retired callback should call removeConfirmingPlayer to handle this case.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[roomote-v0]

SchedulerAdapter.java was deleted in the latest commit (825ac0d) but this file, ConfirmScheduler, and SqlStorageImpl still reference it (TaskWrapper, runTimer, runForEntity, runAsync). The project will not compile. The deletion appears to be accidental and the file needs to be restored.

_{Fix it with Roo Code or mention @roomote and request a fix.}