feat: add combination (AND) blacklist rules

[netcrafts]

What does this change?

Adds combinationBlacklist to the [actions] config section. Each rule is an inline TOML table where all specified fields must match for an action to be suppressed (AND logic). The existing flat blacklists (typeBlacklist, objectBlacklist, sourceBlacklist, worldBlacklist) are evaluated first and are unchanged.

Rules now also support an optional spatial area filter: specify centerX, centerY, centerZ, and range to suppress all actions within a Chebyshev cube of the given radius around a fixed coordinate.

Why?

The existing blacklists use OR logic — adding an entry to any list suppresses every action that matches that single field. This makes it impossible to express rules like "suppress snow golem snow block placements without suppressing all block-place events or all snow interactions". Equally, there is no way to suppress logging within a specific zone (e.g. a spawn protection area) without blacklisting an entire dimension.

How?

CombinationBlacklistRule — data class with optional fields type, world, object, source, centerX, centerY, centerZ, range. Omitted fields are wildcards. matches() returns false for an empty/all-null rule, otherwise ANDs every non-null field against the action. The object field checks both objectIdentifier and oldObjectIdentifier, consistent with objectBlacklist. All four area fields (centerX/Y/Z + range >= 1) must be present together for the area check to apply; a partial spec is silently treated as no area filter.

ActionsSpec — one new required<List<CombinationBlacklistRule>> entry.

ActionType.isBlacklisted() — appends one clause at the end:

config[ActionsSpec.combinationBlacklist].any { it.matches(this) }

migrateConfig() — appendKeyIfMissing() inserts the new key into existing ledger.toml files on first launch after upgrade, so users do not need to manually edit their config.

Config example

combinationBlacklist = [
  { type = "block-place", object = "minecraft:snow", source = "snow_golem" },
  { type = "block-place", object = "minecraft:dirt" },
  { world = "minecraft:overworld", centerX = 0, centerY = 64, centerZ = 0, range = 50 },
]

Backward compatibility

Servers upgrading from an older version do not need to touch their config. migrateConfig() writes the new key (with a commented example) automatically on the first restart after the jar is replaced.