WGA Priority Loot

Added

• A stale-data indicator. /rcpl prio now colors its "Imported: ..." timestamp green/yellow/orange by age (1 day / 3 days), instead of showing a bare date with no sense of how old it is. A raid/party member also now gets a one-time chat warning (per stale streak, not repeated every roster change) if their loaded priority data is more than 3 days old, nudging them to /rcpl sync or ask an officer to /rcpl broadcast a refresh.
• Wishlist tier tags in the officer voting frame's "Full Priority Order" panel. Each ranked name can now show (BiS)/(2nd Choice)/(Sidegrade) (or whatever your team's actually-configured Wishlist Tier Labels say -- pulled from the WGA Raid Hub export, not hardcoded) next to it, so an officer can tell a real BiS pick apart from a lower-tier pick that still made the ranked list, or a rank with no wishlist entry behind it at all (no tag). Loot-council-only by design -- never shown on the raider-facing loot roll frame or the Priority column. Requires a WGA Raid Hub export from after #760; older exports simply show no tags.

Fixed

• The loot roll frame could show a stale, wrong priority rank on a recycled entry widget. RCLootCouncil reuses its own entry widgets across different loot drops that share the same button-config type -- with only a default (Upgrade/Catalyst/OS+M+) and a tier (Gives 1pc/2pc/etc.) type configured, that means any two non-tier items can share one, not just two of the same slot. A trashed widget from an earlier item gets handed to whatever non-tier item drops next, but our Update hook closed over the item from the first time that particular widget was hooked and never refreshed it, so the appended priority text kept describing whatever item the widget was originally created for -- even though RCLootCouncil's own icon/name/ilvl text was correct for the new item. This is the confirmed cause of a report where a raider's loot frame showed "Prio: 3rd" on an item they were actually ranked 14th on (their stored priority data was current and correct throughout -- the display was reading the wrong item). The hook now reads the entry's own current .item field (set by RCLootCouncil itself on every Update call, before any text is touched) instead of the stale closure.
• Item-centric priority lookup could return a same-named player's rank on a different realm instead of your own. The loot frame and voting frame matched the ranked priority list by bare character name as soon as an exact Name-Realm match failed to appear yet, so a raider could see e.g. "Prio: 3rd" when their real rank was 14th, because a different-realm namesake happened to rank 3rd and was scanned first. Exact Name-Realm matches are now always checked across the whole list before falling back to a bare-name match.
• Two prio-sync rejection warnings could spam chat once per roster change, all raid long. Unlike every other warning in Modules/prioSync.lua, the "not the leader" and "keeping your own imported data" rejection messages had no de-duplication, so a client stuck in either state (e.g. a raider who'd previously run their own /rcpl import, now permanently differing from the leader's rebroadcasts) got the same line reprinted on every roster-change resync all night. Both now warn once per distinct rejected payload instead of on every receipt.