[27] Align text emote DB2 fanout gates

[alseif0x]

Refs #50

QA pending: do not merge until capture/manual validation, CI, and Codex reviewer verdict are complete.

Summary:

• Keeps C++-anchored EmotesText.db2 validation and silent return.
• Preserves TargetGUID and aligns player fanout gates with C++ world/map/instance/range checks.
• Re-anchors chat packet comments from C# to C++.

Validation reported locally:

• PROTOC=/home/cdmonio/.local/protoc/bin/protoc cargo test -p wow-world send_text_emote_ --lib
• PROTOC=/home/cdmonio/.local/protoc/bin/protoc cargo test -p wow-world --lib
• PROTOC=/home/cdmonio/.local/protoc/bin/protoc cargo check -p world-server
• cargo fmt --all -- --check
• git diff --check

Manual QA pending: client text emotes with valid/missing/out-of-range target and capture-diff vs C++.

[alseif0x]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: 0193c73f60

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[alseif0x]

QA validation checklist:

• Use common text emotes such as /wave, /dance, /kiss, or /rude near another player/client and confirm nearby players see the expected emote output/animation.
• Repeat with an NPC or creature targeted; valid target-gated emotes should work, invalid combinations should not grant unexpected behavior.
• Try an emote with no target and with an out-of-range target if practical; it should not crash or send obviously wrong fanout.
• Verify normal chat, targeting, movement, and combat remain unaffected.

Checks are currently green; leave final status pending user QA.