Add controllable name tag display setting for custom name tag compatibility

[Copilot]

This PR adds a new player setting that allows users to disable Neptune's built-in name tag display system, making it compatible with custom name tag implementations.

Problem

Users with custom name tag plugins experienced conflicts with Neptune's health display system that uses DisplaySlot.BELOW_NAME. When Neptune shows health information below player names, it interferes with custom name tag implementations, making them unusable.

Solution

Added a new Name Tag Display setting that players can toggle in their settings menu. When disabled, Neptune will not show health information below player names, allowing custom name tag systems to work without conflicts.

Key Features

• Player Control: Individual players can toggle name tag display on/off in the settings menu
• Real-time Updates: Changes take effect immediately, even during active matches
• Backward Compatibility: Defaults to enabled, so existing users see no change in behavior
• Respects Kit Rules: Only affects kits that have the SHOW_HP rule enabled
• Clean Integration: Follows existing setting patterns exactly (same as Player Visibility, Menu Sounds, etc.)

Implementation Details

The setting is implemented across 4 files following Neptune's established patterns:

1. SettingData: Added showNameTag boolean field (defaults to true)
2. MenusLocale: Added configuration entries for the setting UI (slot 17, NAME_TAG material)
3. Setting: Added NAME_TAG_DISPLAY enum entry with toggle logic and immediate match updates
4. Match: Modified health display methods to respect individual player preferences

Usage Example

// Before: Custom name tags conflict with Neptune's health display
// After: Player goes to Settings → "Name Tag Display" → Toggle off
//        Custom name tags now work perfectly without conflicts

Players who prefer Neptune's built-in health display can leave the setting enabled, while those with custom implementations can disable it for full compatibility.

Fixes #70.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• jitpack.io
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/Neptune/Neptune org.codehaus.plexus.classworlds.launcher.Launcher clean compile (dns block)
• mvnrepository.com
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/Neptune/Neptune org.codehaus.plexus.classworlds.launcher.Launcher clean compile (dns block)
• repo.aikar.co
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/Neptune/Neptune org.codehaus.plexus.classworlds.launcher.Launcher clean compile (dns block)
• repo.codemc.io
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/Neptune/Neptune org.codehaus.plexus.classworlds.launcher.Launcher clean compile (dns block)
• repo.extendedclip.com
• repo.papermc.io
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/Neptune/Neptune org.codehaus.plexus.classworlds.launcher.Launcher clean compile (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

@Devlrxxh 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.