Fix donated points calculation using stale stored total instead of current block values

[Copilot]

The donated block points were accumulated in the DB at donation-time block config values. When an admin later changes block values, tidyUp() was still using the stale stored total — causing level calculations where the reported total was less than a single block type's current contribution (e.g. total = 49,348 while Iron Block alone = 3,553 × 14 = 49,742).

Changes

• IslandLevelCalculator.tidyUp(): Replace the stale getDonatedPoints() DB read with a dynamic recalculation from the donatedBlocks count map × current block config values. Keys are lowercased to match the stored config format.

// Before
long donatedPoints = addon.getManager().getDonatedPoints(island);

// After — always reflects current block config
Map<String, Integer> donatedBlocksMap = addon.getManager().getDonatedBlocks(island);
long donatedPoints = donatedBlocksMap.entrySet().stream()
        .mapToLong(entry -> {
            Integer value = addon.getBlockConfig().getValue(island.getWorld(),
                    entry.getKey().toLowerCase(java.util.Locale.ENGLISH));
            return (long) Objects.requireNonNullElse(value, 0) * entry.getValue();
        })
        .sum();

• getReport(): Updated the per-block value lookup to use getValue(world, key) (world-specific) instead of the flat getBlockValues() map, making the report consistent with the calculation.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud