Remove emojis and clarify GABP compliant mod architecture in documentation

[Copilot]

This PR addresses documentation clarity issues by removing emojis and better explaining how GABS connects to game modifications.

Changes Made

Emoji Removal

• Removed all emojis from README.md and AGENTS.md headers and bullet points
• Maintained clean, professional documentation style throughout

Enhanced GABP Compliance Clarity

• Updated all references to specify "GABP compliant modifications" instead of just "game mods"
• Added clear explanation that mods must implement the GABP protocol to work with GABS
• Updated architecture diagrams to show GABP Compliant Mod in the data flow

New Mod Architecture Documentation

Added comprehensive explanation of different GABP compliant mod types that GABS can connect to:

1. Central Community Mods: Single mods that search for and expose tools from all other installed mods
2. Individual Framework Mods: Specific mods using GABP framework to expose their own functionality
3. General Game Control Mods: Mods that make entire games remotely controllable
4. Combined Control Mods: Mods providing both game control and mod-specific functionality

This clarifies that GABS can provide fine-grained control over specific mod functionality, broad control over entire games, or any combination depending on the mod architecture chosen.

Technical Details

• All existing functionality preserved
• No breaking changes to code or APIs
• Go build verification confirms no compilation issues
• Maintains same document structure and information flow

The documentation now clearly communicates that GABS acts as a bridge to GABP compliant game modifications, removing ambiguity about compatibility requirements and supported architectures.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.