Bug/Workaround of The Chasm region being displayed as Liyue

[Artprozew]

When the player teleports to The Chasm, the log will report that region for us. But after some time, it will report the region as Liyue, even if the player is still in The Chasm.

For now, this bug is being worked around by:

GenshinRichPresence/src/main.py

Lines 208 to 212 in ba32dac

	if self.region == "liyue" and self.previous_region == "the_chasm":
	# Workaround: ensure the player's region is set to "The Chasm" instead of "Liyue"
	# But, it will still report "The Chasm" if the player teleports FROM The Chasm to Liyue.
	self.logger.debug("Setting region as the_chasm because of previous region")
	self.region = "the_chasm"

This code will ensure that the player's region is set to The Chasm if the log reports the region as The Chasm first but then reports Liyue after.
But this introduces another issue. It will still set the region as The Chasm if the player teleports FROM The Chasm to Liyue.

This issue may be related to world hashes, but needs further investigation.

[Artprozew]

Investigating further, I found that the issue was caused by the log reporting the Noctilucous Jade (hash 251c33d0) which is in The Chasm, but is associated with the Liyue region. The Chenyu region also has that problem when the log reports Violetgrass (hash f0aaaa18). One way to deal with this is to not include those two hashes on the world data .ini file, but this would also make the region detection less frequent and more restrictive, so I will have to decide wether or not we will stick to that or continue to workaround with better methods.