temporal: prohibit writing map timestamps across mapsets

[Dasux]

This PR addresses issue #3394

The problem was when registering a map like lakes@PERMANENT , the temporal framework attempts to write timestamp data into the current mapset. This created an invalid map entry e.g, lakes@to_verify without the actual vector data.

The reason was ... the function write_timestamp_to_grass() is called without verifying that the map belongs to the current mapset.

Fix made:

Added an additional condition in the function update_absolute_time()... to verify if map is in its own mapset or not.

if (
                get_enable_timestamp_write()
                and self.get_mapset() == get_current_mapset()
            ):
                self.write_timestamp_to_grass()
            else:
                self.msgr.warning(
                    f"Skipping timestamp write for {self.get_map_id()} (different mapset)"
                )

Additional note:

I found multiple instances of write_timestamp_to_grass ... I've added the condition only in one of the methods... I wanted to confirm if this was the intended change required before proceeding with the other methods...

[ninsbl]

Looks good to me. Have not tested if it completely fixes the issue. But it is an improvement in any case...

[Dasux]

Thanks for the feedback,

currently it does not work as intended... lakes@to_verify still shows up in the vector list .... since i only applied the condition to one method//

I'll get back to you after i append the changes to the other methods