Emote Update

This update focuses on the new emote pack registration system, pack.json-based loading and permission handling, improved reload behavior, and overall server management cleanup.

---

New Features & Improvements

Added pack.json-Based Emote Pack Registration

• Added a new pack.json configuration file.
• Emote packs are now registered using the values defined in pack.json, including datapack_identifier, name, command_name, description, and default_animation_name.
• This makes pack metadata easier to manage in one place.

Datapack Loading Now Uses Registered Packs Only

• Datapacks are no longer loaded automatically just because they exist in the datapack folder.
• Only namespaces registered in pack.json are treated as valid and loadable emote packs.

Improved Permission Mapping

• Permission mapping has been updated.
• Namespace-based permissions are now built from the permissions section in pack.json.
• Pack registration and permission settings are now managed in a more consistent structure.

---

Admin & Server Management Changes

Expanded /emote reload Behavior

• /emote reload now reloads both config.json and pack.json.
• It also reapplies datapacks and refreshes skin server settings.
• The result message now includes cfg=..., identifier=..., and emotes=..., with (resource reload) shown when applicable.

Removed Automatic Cleanup of Legacy Shortcut Datapacks

• The old automatic cleanup logic for legacy emote-dialog-shortcut datapacks has been removed.
• If those files or folders still exist, they must now be removed manually.

---

Internal Changes

Reorganized Server Initialization Structure

• Server initialization has been restructured.
• Command registration, network setup, lifecycle handling, and skin sync logic are now separated more clearly for easier maintenance.

Reworked Skin Synchronization Flow

• Emote skin synchronization has been restructured.
• Skin and playback state are now managed through separate services and a new network/listener flow.