wxGUI/history: Display saved region name if stored

[saket0187]

This PR adds the feature referred in #5283

Here are the outputs:

• When it matches in MAPSET/windows

• When it doesn't match in MAPSET/windows

Added two new methods to support region name display:

• _get_saved_region_name(): Searches MAPSET/windows for matching saved regions
• _compare_regions(): Compares regions with epsilon tolerance for floating-point precision

These methods are separate from the existing region match logic to avoid modifying
working functionality and keep changes minimal and isolated.
Let me know if this needs any changes.

[wenzeslaus]

The comparison needs more reasoning (epsilon, 3D, ...). Similarly, please describe behavior for the different situations.

As for the details here, user may still want to update to the named (saved) region. The GUI element alignment is wrong.

[saket0187]

Thank you for the review. Just wanted to clarify few things before making commit.

The comparison needs more reasoning (epsilon, 3D, ...). Similarly, please describe behavior for the different situations.

I assume this means I should compare all other values like 3d items. right?

As for the details here, user may still want to update to the named (saved) region. The GUI element alignment is wrong.

Can you explain this a little more what do you mean here if you don't mind.

[wenzeslaus]

Yes, you should also compare the values for 3D.

[saket0187]

I know there are still some changes needed, but I wanted to check if I’m heading in the right direction or just overcomplicating things.

Currently, history.py command info provides 2D region values as far as i was able to understand. I modified it to return 3D values by using region3d=True.

I also switched to format="shell" instead of JSON because the JSON output was returning verbose keys like "north" instead of short keys like "n", which simplifies parsing.

Additionally, I added translation keys for the new 3D fields, although these can be removed if not needed.

From what I could find , when region 3D values aren’t present, they are set to defaults automatically, so converting from a 2D region to 3D will provide reasonable default values right?