Native NBT Integrity System: Fix for Item Spoofing and Duplication

Current Issue: Vanilla servers (including Realms) lack server-side validation for NBT data sent via Creative packets. This allows malicious clients to inject "god-items" (e.g., Sharpness 255) and perform duplication exploits using BlockEntityTag. ​Proposed Solution: ​NBT-Checker: Server-side validation that reverts attributes/enchantments to game-defined limits. ​NBT-Reset (Sanitizer): Automatic stripping of nested container tags from unauthorized client packets. ​NBT-Register: A strict whitelist of server-recognized NBT tags; all foreign tags are discarded. ​NBT-Core Data Caps: A hard limit on NBT size per slot to prevent buffer-overflow crashes. ​Goal: To make Minecraft multiplayer secure "out of the box" and protect server economies without relying on 3rd-party plugins like Paper or Panilla.