Fix auto-generated messages above player's head

See merge request !19

Player Data Refactor: Particles, Sounds, and Data Enhancements

See merge request !18

Added new lead_friend and lead_enemy particles and sounds, to make it clear when a "lead" behavior begins

Broadcast story set/clear/display to all ops. Also, add a new "story display" command, which prints the current story.

Broadcast ALL player friendships with each message update (to keep client in sync with server). Also updated many log statements, to improve debug output.

Added NULL checks on client message listeners (to prevent crashes for invalid or uninitialized clients)

Fixing PACKET_S2C_MESSAGE from crashing a newly logging on player, if they receive that message first.

Additional refactor around playerData and friendship and player messages - trying to fix an issue with friendship not updating correctly

More fixes for regressions related to player message bubbles. Seperated `generateCharacter()` and `generateMessage()` functions for simplicity

Do not broadcast system-character messages to all players, or it will display the request to generate a character for no reason

Fixing another regression found during testing, user messages were breaking due to missing "playerName" attribute

New `/creaturechat story` command to customize the character creation and chat prompts with custom text.

When entity conversations switch players, a message is added for clarity (so the entity knows a new player entered the conversation). Entity's now keep their entire message history in a single stack, but have more context when player's change in the conversation.

Additional regressions caused by switching from UUID to player's display name (nick). Also, setting "born" and "death" timestamps, and no longer deleting chat data.

Refactor messages back to a single List<ChatMessage>, but now with a "name" attribute based on Player's display name. This will more easily allow for filtering the list of messages by player name, and also allow for more role playing (i.e. changing nick on a server can change your friendship / message history).

Adding timestamps to ChatMessage (long based unix timestamp format), also sets them during migration

Limiting LEAD particles to 3, and move them further in front of the entity. Also scale LEAD particle smaller.

Fixed a bug causing new player data to not be saved (breaking the chat requests). Now new players will always start with the original greeting and be saved in the player data with a new UUID.

New animated lead particle (arrows pointing where they are going). New animated attack particles with random # of particles.

New follow, flee, attack, and protect particles & sound effects. Protect now auto sets friendship to 1 (if <= 0), to prevent entity from attacking and protecting at the same time. Passive entities no longer emit damage particles when attacking, they emit custom attack particles

Initial custom particles, and a custom particle type and factor for friendship particles (heart and fire)

Small refactor to playerData args, and a fix to prevent "" blank player from being in every entitychatdata. It should only exist with migrated data. Also made the old legacy JSON properties disappear after saving this new data structure.

Fixing EntityChatDataLight, to correctly inflate from the full EntityChatData instances, including the current playerData.

More refactoring around PlayerData and player-based friendship. Also, adding in migration of data from entity-based friendship to player-based.

Large refactor of EntityChatData, EntityChatDataLight, and ChatDataManager. Separating these into smaller, individual files, to make it easier to maintain.

Fixing deploy scripts for both Modrinth and CurseForge

See merge request !17

1.1.0 Release w/ Lead behavior

See merge request !16