Modified the _config_get function to properly handle nested YAML values.

[SamuelWN]

The OmegaConf's get function does not appear to handle nested YAML values as expected.
Instead of interpreting the value to the left of . as the parent key, it seems to interpret it literally (e.g. searches for a key named chatgpt.chat_system_template).

The select function is able to handle nested values (and searches top-level keys with . if _CONFIG_KEY is empty). However, it will not search upward for the key, and instead returns None, so get is still required.

ToDo: Move gpt_config stuff to a parent class

[popcion]

@SamuelWN
After this PR was merged, all subsequent versions in server produced an "INFO: Could not find files for the given pattern(s)", but it doesn't affect the actual running of the program. Do you have any ideas about this?

[SamuelWN]

@popcion I have never actually used the web mode and haven't ever gotten that message when using the command line.

I searched for that error message, and the most likely culprit I found was:

manga-image-translator/manga_translator/translators/__init__.py

Lines 67 to 69 in 9cc3908

	def get_translator(key: Translator, *args, **kwargs) -> CommonTranslator:
	if key not in TRANSLATORS:
	raise ValueError(f'Could not find translator for: "{key}". Choose from the following: %s' % ','.join(TRANSLATORS))

Though introduced only in a later merge (not this one), I could imagine that warning being triggered if the user provides openai as the translator (rather than "chatgpt"). Though intended nice and easy way to allow alternate names, I could imagine it confusing the other code:

manga-image-translator/manga_translator/config.py

Lines 138 to 143 in 9cc3908

	# Map 'openai' and any translator starting with 'gpt'* to 'chatgpt'
	@classmethod
	def _missing_(cls, value):
	if value.startswith('gpt') or value == 'openai':
	return cls.chatgpt
	raise ValueError(f"{value} is not a valid {cls.__name__}")

If changing the translator to chatgpt gets rid of the warning, then that is probably the cause.

[popcion]

Thank you for your analysis, but after trying, this info still occurs. I saw this issue on a Discord server, and it still exists.
Before this PR was merged:

After merging:

However, when I tested it with Python 3.10 on Linux, it didn't show up. I'm using Python 3.11.4 on Windows, and I'm not sure yet if it's a version issue.