[CI test] Combined ports of CivMC PRs #916/#917/#918

[grepsedawk]

This PR exercises the Gradle Check All workflow on the combined set of three ports:

• EdenMinecraft/Civ#19 — Fix emeralds blocking chest interactions
• EdenMinecraft/Civ#20 — Show days remaining on pearls
• EdenMinecraft/Civ#21 — Repair the Gradle test suite and run it on PRs

Base: eden-main (snapshot of EdenMinecraft/Civ's main).
Head: eden-test-combined (the three branches merged together).

Local ./gradlew check is green; this PR exists so CI runs the same suite.

[gemini-code-assist]

Code Review

This pull request introduces JUnit 5 testing infrastructure across several plugins, integrating MockBukkit for civmodcore-paper and adding comprehensive unit tests for exilepearl-paper. It also implements a "Time remaining" display in Exile Pearl lore and refactors interaction handling in OldEnchanting to allow sneaking players to interact with blocks. The reviewer identified a critical issue with the JUnit versioning scheme in libs.versions.toml where a non-existent version 6.0.3 was used, suggesting splitting the Jupiter and Platform versions. Additionally, a guard clause improvement was suggested for PearlDecayMath to handle non-positive configuration values robustly.

[gemini-code-assist]

JUnit 5 (Jupiter) and JUnit Platform use different versioning schemes (e.g., Jupiter 5.10.3 and Platform 1.10.3). There is no version 6.0.3 for either, and using a single version reference for both will cause dependency resolution to fail. We should split them into separate version properties.

Suggested change

	junit = "6.0.3"
	junit-jupiter = "5.10.3"
	junit-platform = "1.10.3"

[gemini-code-assist]

Update the JUnit dependency definitions to use the split version references (junit-jupiter and junit-platform) to avoid resolution errors.

Suggested change

	junit-api = { group = "org.junit.jupiter", name = "junit-jupiter-api", version.ref = "junit" }
	junit-engine = { group = "org.junit.jupiter", name = "junit-jupiter-engine", version.ref = "junit" }
	junit-platform-launcher = { group = "org.junit.platform", name = "junit-platform-launcher", version.ref = "junit" }
	mockbukkit = { group = "org.mockbukkit.mockbukkit", name = "mockbukkit-v1.21", version = "4.93.0" }
	junit-api = { group = "org.junit.jupiter", name = "junit-jupiter-api", version.ref = "junit-jupiter" }
	junit-engine = { group = "org.junit.jupiter", name = "junit-jupiter-engine", version.ref = "junit-jupiter" }
	junit-platform-launcher = { group = "org.junit.platform", name = "junit-platform-launcher", version.ref = "junit-platform" }
	mockbukkit = { group = "org.mockbukkit.mockbukkit", name = "mockbukkit-v1.21", version = "4.93.0" }

[gemini-code-assist]

To prevent unexpected behavior or negative values from misconfiguration, we should also guard against non-positive values for humanIntervalMin and decayAmount.

Suggested change

	static int decayPerHumanInterval(int humanIntervalMin, int decayIntervalMin, int decayAmount) {
	if (decayIntervalMin <= 0) {
	return 0;
	}
	return (humanIntervalMin / decayIntervalMin) * decayAmount;
	}
	static int decayPerHumanInterval(int humanIntervalMin, int decayIntervalMin, int decayAmount) {
	if (decayIntervalMin <= 0 || humanIntervalMin <= 0 || decayAmount <= 0) {
	return 0;
	}
	return (humanIntervalMin / decayIntervalMin) * decayAmount;
	}