Describe the bug
A player who changed his name to match a previously used name caused an exception in Prism.
See https://pastebin.com/kju1czbr

To Reproduce
Player A joins with UUID 1
Player B joins with UUID 2
Player A renames his account to B
Player B joins with UUID 1 - Exception thrown and prism_players table is left with Player B UUID 2
(Note this occurred over a 12 month period)

Expected behavior
Prism should handle this as a matter of course and have the correct data in prism_players. Also note that at this point UUIDs 1 and 2 both have the same player name. prism_players should handle this properly. (I guess lookups for the original Player B are no longer possible?)

Server (please complete the following information):

• Prism Version: v2.1.7-
• Server Type: Spigot
• Server Version: git-Spigot-628435a-b5e5adc (MC: 1.16.4)

Stupid Github hiccup.