Refactor PDCDupeManager persistant data type for dupe key

[Xefreh]

This pull request aims to use a boolean value for the dupe key in PDC, similar to what the NMSDupeManager already implements.

[Copilot]

Pull Request Overview

This PR refactors PDCDupeManager to use a boolean flag for the dupe key instead of an integer, matching the implementation in NMSDupeManager.

• Switches PersistentDataType.INTEGER to PersistentDataType.BOOLEAN when setting the dupe marker.
• Updates the existence check to use the BOOLEAN type.

Comments suppressed due to low confidence (2)

src/main/java/fr/maxlego08/menu/dupe/PDCDupeManager.java:60

• Add unit tests covering both the new BOOLEAN-based flow and a fallback or migration path for INTEGER-backed items to ensure proper detection across versions.

        return persistentDataContainer.has(this.namespacedKey, PersistentDataType.BOOLEAN);

src/main/java/fr/maxlego08/menu/dupe/PDCDupeManager.java:37

• Existing items tagged with the old INTEGER value will no longer be recognized as dupes. Consider adding a fallback check for INTEGER or migrating legacy data so previously marked items remain detected.

            persistentDataContainer.set(namespacedKey, PersistentDataType.BOOLEAN, true);