chore(#26636): extend logging for GetClosestGraveyard() (#1)

[stdNullPtr]

Changes proposed:
Extend logging in the GetClosestGraveyard () function to include player GUID for traceability.

Issues addressed:

Closes #26636

Tests performed:

Builds, tested in game.

[CraftedRO]

while player guid is good, I think @Aokromes probably reffers to name of that player (if that's possible).

[stdNullPtr]

while player guid is good, I think @Aokromes probably reffers to name of that player (if that's possible).

@CraftedRO I was thinking about it, but this will produce an invalid log message if the player is renamed right? You will have to do extra work if you are going through old logs, to track any renames to follow the path to the real player. The guid provides proper traceability in my opinion.

[Aokromes]

well, it's not like people renames a lot xd also, if name not found guid can be search.

[stdNullPtr]

@Aokromes up to you guys, would you like me to log only name? Or GUID + name?

[Aokromes]

imho both.

[stdNullPtr]

imho both.

Done, this should be ok:

ZoneId not found for map 571 coords (-1810.8016, -4850.331, -1.839498), player name: (Ludnica) player GUID: (GUID Full: 0x0000000000000001 Type: Player Low: 1)

It's my first contribution so don't hesitate to request as much changes as needed, even for little things.

Edit: I forgot to pass the GUID as const ref as well... I will adjust in a few days, don't have access to PC for a while.