Optionally accept precise OMT coordinates in debug "Teleport - to specific overmap" function

[Stu33]

Summary

Interface "Optionally allows a specific overmap tile to be specified for the debug 'Teleport - to specific overmap' function."

Purpose of change

It is sometimes useful to teleport to a specific overmap tile, either when testing or when cheating/working around an issue. The existing 'teleport to specific overmap' option in the debug menu takes single integer x and y coordinates separated by a comma specifying a whole overmap (128x128 block of OMTs). Extending this syntax so that the existing overmap teleport works in the same way as before but more precise OMT coordinates can be used if desired makes it more useful.

Describe the solution

Extend parsing to understand the OMT coordinate system used in the overmap display - an integer overmap coordinate followed by a single quote/apostrophe and then an integer OMT offset within the overmap for each of x and y. If no OMT offset is given then a value of 0 is used, giving the same behaviour as existed previously. So you can now choose to teleport to 1'123,0'42 instead of just 1,0.

Describe alternatives you've considered

Not doing this. You can still reasonably quickly teleport to a specific OMT by teleporting to the origin of an overmap and then using the 'Teleport - Long Range' option to precisely select an OMT on the overmap view.

Testing

Used the feature to teleport around the map. Also checked that just specifying overmap coordinates as integers and that using optional integer z-coordinates continues to work as before.

Additional context

[GuardianDll]

Can you resolve clang tidy errors?