ItemBlackListFIXED

# Changelog

## PR: Add independent crafting and placement item rules

- Added permanent craft-output exceptions, placement-only bans, and
  crafting-input-only bans with registry IDs, exact or wildcard metadata, and
  the existing global/dimension selector syntax.
- Persisted the three rule types in separate world JSON files, included them in
  reloads and the shared administrative/public list display, and added all six
  add/remove commands with help and tab completion.
- Reused the server-authoritative `Container.slotClick` guard to inspect the
  cached `SlotCrafting` matrix, while placement-only enforcement uses Forge
  place and multi-place events without packing or consuming the item.

## PR: Broadcast timed expirations and add a configurable public ban list

- Broadcast each runtime timed world-ban expiration with its registry item,
  metadata, and global or dimension scope while keeping startup/reload cleanup
  silent.
- Added the read-only `/banlist [dimension|__GLOBAL__]` command with shared
  world/pack list rendering and timed-expiration details.
- Added the op-only `/itemblacklist publiclist [on|off]` toggle, defaulting to
  enabled and persisted in the normal Forge configuration.

## PR: Add timed and scheduled item unbans

- Added optional `timer <duration>` and `date <MM-dd-yyyy> <time>` suffixes to
  world `ban` and `meta`, including rescheduling and conversion to permanent.
- Persisted UTC expirations as optional `expiresAt` entry properties while
  retaining permanent-entry and legacy `damage` JSON compatibility.
- Added server wall-clock matching, one-second server-thread cleanup,
  restart/reload cleanup, and immediate online inventory/container refreshes.
- Documented scheduling units, syntax, time-zone behavior, and persistence.

## PR: Add held-item metadata ban commands and canonical JSON metadata

- Added `/itemblacklist meta` and `/itemblacklist unmeta` to create and remove
  exact held-item metadata bans across the existing dimension selectors.
- Kept held-item `/itemblacklist ban` wildcard behavior and explicit registry
  item metadata syntax.
- Made `meta` the canonical JSON property while retaining validated support for
  legacy `damage` entries and wildcard defaults.
- Documented metadata-specific dye and bonemeal bans.

## PR: Show the banned-item message for crafting clicks

- Display the configured banned-item message when a player attempts to take a
  banned crafting result.
- Document the crafting-click feedback and its configuration source.

## PR: Fix GTNH coremod class resolution

- Made the configured coremod class relative to `modGroup`, allowing the GTNH
  convention plugin to resolve the existing loading plugin correctly.

## PR: Enforce banned crafting results with a Forge coremod

- Banned crafting results can no longer be extracted while a crafting GUI
  remains open.
- Blocked results remain visible using the existing banned-item representation.
- Crafting-result click prevention is server-authoritative, including direct
  window-click packets and every vanilla container click mode.
- Banned crafting-result extraction is enforced through a small Forge 1.7.10
  coremod hook.